Use Peribolos for declarative GitHub Organisation management
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 0
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 2
Description
Peribolos is a CI utility maintained by the people at k8s that enables declaratively defining the GitHub Organisations' settings through a YAML file.
Benefits of adopting the declarative approach:
1. Better visibility on changes made and the discussion surrounding it through Pull Requests
2. Reduce the permissions needed by the maintainers
3. Allows anyone to suggest amendments and audit the GitHub Organisation without needing administrative privileges
4. Enforce certain users to be admins
5. Allow management of multiple GitHub Organisations through a single pane of glass
An example of Peribolos implemented with GitHub Actions:
https://github.com/cloudfoundry/community/blob/main/.github/workflows/org-management.yml
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the referenced Cloud Foundry example at .github/workflows/org-management.yml and the Peribolos documentation. Determine how the LoopBack GitHub Organisation settings should be represented in YAML and managed through GitHub Actions. Done means the organisation is managed declaratively and changes can be proposed and audited through pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, yaml
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100