<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Directory management :: R-Ladies organizational guidance</title>
    <link>https://guide.rladies.org/global-team/directory/index.html</link>
    <description>The R-Ladies directory source data is in a private repository containing potential personal information. If you have a local clone of this, please ensure it is stored securely.&#xA;Notes to Self Entries from Males: Consider how to handle entries submitted by males. Should we delete these files during editing/reviewing? Previewing Updated Files: Ensure a method to check updated previews once files are changed.</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://guide.rladies.org/global-team/directory/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Updating entires</title>
      <link>https://guide.rladies.org/global-team/directory/update-entries/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://guide.rladies.org/global-team/directory/update-entries/index.html</guid>
      <description>Each directory entry must be reviewed and approved before it becomes visible on the R-Ladies Directory website.&#xA;On a weekly basis, an automated process runs to pull new entries from the R-Ladies Airtable form and create a Pull Request (PR) in the R-Ladies Directory repository (the repo is private and only accessible to R-Ladies Global website and directory teams). This typically happens on Thursday evening Eastern Time (ET) or Friday morning Central Europe Time (CET). The PR will auto-assign the PR to a directory team member, who will then review the entries and merge them into the main branch if everything looks good.</description>
    </item>
    <item>
      <title>Deleting Entries</title>
      <link>https://guide.rladies.org/global-team/directory/delete-entries/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://guide.rladies.org/global-team/directory/delete-entries/index.html</guid>
      <description>In our project, maintaining a clean repository history is crucial, particularly because the R-Ladies directory contains personal information. It is essential to ensure that any entries that need to be removed are purged from both the current state of the repository and its history. This practice is vital to prevent any accidental exposure of sensitive information, uphold data integrity, and comply with data protection regulations.&#xA;The process for purging entries is managed through a series of automated GitHub Actions. These actions are designed to effectively delete specified entries while ensuring that both the current repository state and its history are updated accordingly.</description>
    </item>
    <item>
      <title>GitHub Actions</title>
      <link>https://guide.rladies.org/global-team/directory/github-actions/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://guide.rladies.org/global-team/directory/github-actions/index.html</guid>
      <description>The directory management process is enhanced through the use of GitHub Actions, which automate various tasks related to fetching, validating, and purging entries from Airtable. Below is a detailed overview of the GitHub Actions implemented for managing the R-Ladies directory.&#xA;Fetch Entries from Airtable This GitHub Action is designed to automate the process of fetching entries from Airtable and updating the directory in our repository.&#xA;Here’s a simple breakdown of what this action does:</description>
    </item>
  </channel>
</rss>