In order to keep things consistent over the development of the project these are the rules every member should follow:
- For every feature/US a new branch must be created.
- In the end of each sprint create a branch named snap-sprint-X.
Branch names & commit messages:
purpose(specification[optional]): descriptive message
Note: Branch naming uses dash case branch-name ✔️ branchName ✖️
Example:
feat: added vaccine scheduling system
or
docs(readme): added new us07 specifications
or
feat(tests): added new tests to us07
- feat: a new feature is being added
- fix: something broken is being fixed
- docs: documentation changes
- refactor: changes to the code organization
- test: new tests were added/changed
- chore: minor code changes that does not impact functionality (Ex. removing/adding blank lines)
git add -p - It helps to separate large code changes in small commits. An iterative menu is presented to select what code pieces you want to add to a given commit.
git branch -b branch-name - Creates a branch named branch-name
git status - Lists all changed files
git branch -a - Lists all branches in the repository
git checkout branch-name - Change from current branch to branch-name
git diff branch1..branch2 - Compare two branches