Page History

...

Replace <organization> and <repo> with the proper names in the recipe below. You will need to push every branch that you need. Below is just an example for code created at SLAC, but customized code from the community will have different branches than this example. Don't forget to add --tags to the push command. For code created at SLAC, use the -u argument for the pre-release branch. This will make it the default branch.

git remote add github-origin https://github.com/<organization>/<repo>.git
git push -u github-origin main --tags
git push -u github-origin pre-release --tags

...

• Click on Settings.
• Click on Collaborators and teams.
• Click on Add teams.
• Search for the group tid-cds-acs and make this group admin of the repository.
• This is only for code created at SLAC and not for code from the community:
  • Still in the Settings page, click on the General link on the menu on the left. 
  • Find the section Default branch. Change from If it is not pre-release, change from main to pre-release. This is to avoid accidental clones starting at main and pull requests made at main.
  • Still in the Settings page, click on the Branches link on the menu on the left. 
  • Click on Add branch protection rule.
  • For the main branch:
    • Branch name pattern: type main in this field.
    • Check these boxes:
      • Require a pull request before merging
      • Require approvals
      • Require conversation resolution before merging
      • Lock branch
    • Click on Save changes.
  • For the pre-release branch:
    • Branch name pattern: type pre-release in this field.
    • Check these boxes:
      • Require a pull request before merging
      • Require approvals
      • Require conversation resolution before merging
    • Click on Save changes.

...