Overview: The purpose of this diagram is to show the workflow that one would follow for performing a few actions on new repositories within a new GitHub organization.
- Lock master branch when a new repository is created. This is to ensure best practices are followed and pull requests are being made for committing to your master branches
- Create a notification via a issue within newly created repository
Enhancements:
- Check the master branch isn't empty
- Verify the master branch can't be committed to
- Additional notifications (ie Slack notification)
- Add code to Jenkinsfile to perform API actions