Repository Management
Repository Management
How to properly set up the git repository for a new project
Git Repository Naming
Follow guidelines from Repository Naming Conventions for clear, consistent repository names.
Archive the repository when it will no longer be maintained. In addition, add a prefix z-archived to archived/deprecated/unused repositories to put them last in sorting. For example: z-archived-cozmo-manager.
Check the setting up docs for setting up IDE, virtual environment, formatters and linters in a new repository.
Branches
- main – for latest stable releases
- dev or develop – active work on features
- staging – pre-release system testing and QA
- release/XXX – specific release branches
Access management
- Give only as much access as needed. Do not give write access if a person does not need it.
- Use GitHub organization teams to give access to whole teams instead of adding one-by-one.
- Only DevOps people and seniors should have access to repository secrets.