Out of use as it is deemed to be repetitive waste of GitHub API calls and resources for repositories that are once set to be configured. Might convert this to a script to be run on creation of repositories later.
- It is hard to maintain consistency across all repositories
- This will sync all the repository settings
- It supports
labels,rulesets,webhooksand more...
The GitHub Action sync.yml will run every day and sync the repository settings with the config.
- Finds labels from the config in
config/labels.jsonand creates them if not found, else updates them. It will also delete the labels which are not in the config. - It will also sync the colors of the labels.
- The key of the label for syncing is the
nameof the label.
- If the repository has projects enabled, it will disable them if they are not used.
- It will set the merge strategy to
squashandrebasefor the repository. - Merge commits are not allowed.
- Auto-merge is enabled for the repository.
- Branches are deleted after merging.
- Web commit signing is required.
- First, It will also delete all the rulesets.
- Then it will create the rulesets from the config in
config/rulesets.json.
- Webhooks are only
CREATEDandUPDATED. - The key for syncing the webhooks is the
urlof the webhook. - The config is in
config/webhooks.json.
- It will set the permissions for the
actionstowritefor the repositorys. - It will allow the
actionsto access the approve pull requests.
- It will check if the repository has a
README.mdfile or not. - If not, it will make a issue and ask the user to add a
README.mdfile.
It will not create duplicate issues for the README.md file if the issue is already open and the title of the issue hasn't changed.
- It will check if the repository has a
LICENSEfile or not. - If not, it will make a issue and ask the user to add a
LICENSEfile.
It will not create duplicate issues for the LICENSE file if the issue is already open and the title of the issue hasn't changed.
This project is licensed under the GNU-GPLv3.0+ license. Read the license file for more details
