Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: terminology added #184

Merged
merged 12 commits into from
Oct 18, 2023
14 changes: 14 additions & 0 deletions docs/maintainers/setting-up-a-new-repository.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,20 @@ Then go back to your repository and delete:
- πŸ‘€ needs-triage (green background one)
- other potential duplicates if the above race condition is different

> In this context, `race condition` refers to a situation where multiple labels are being deleted simultaneously. This can cause issues if the order in which the labels are deleted affects the final outcome. Therefore, it's important to ensure that the deletion of labels is properly synchronized and controlled to avoid any race conditions.

In other words, if two of the directories (e.g., `πŸ‘€ needs-triage` and `documentation` are deleted at the same, it is possible that the third directory(`potential duplicates`) will not be deleted.
To avoid the `race condition`, the code must delete the directories in a specific order. For example, it could delete the `documentation directory` first, then the `πŸ‘€ needs-triage` directory, and then the other `potential duplicates` directory.

Here is an example of how to delete the directories in a specific order:
```bash
rm -rf documentation
rm -rf πŸ‘€-needs-triage
rm -rf other-potential-duplicates
```
This code will ensure that all three directories are deleted, even if the code is interrupted while it is running.
Lymah123 marked this conversation as resolved.
Show resolved Hide resolved


## Syncing branch protections with opensauced.pizza

This topic is more complex but in a sense tap the main branch and enable
Expand Down