-
Notifications
You must be signed in to change notification settings - Fork 0
Branching and Commits
This repo is working in Git Flow specification. There are two work branches: develop and main.
These branches are rule-protected on GitHub. Check out repo's settings for details.
Custom branch naming pattern based on Git Flow: [branch-type]/[ticket-id]-[description-in-kebab-case]
As a developer, you will need to know how to create release, hotfix and feature branches.
To create branch based on ticket:
- Enter ticket's screen on GitHub,
- On right metadata's column, find "Development" section,
- Click on "Create branch" link,
- GitHub will generate most of branch's name, just rearrange it to follow required naming convention,
- Click "Create branch",
For Refactor Request create "hotfix" branch.
Branches must always be created from develop, main branch is only used for releases.
This repo is working in Conventional Commits standard. Use correct type, based on changes performed.
This project is using given types:
- feat: A new value,
- fix: A bug fix,
- refactor: A change, that neither fixes a bug nor adds a value,
- chore: Perform changes, that are not visible to user,
- docs: Documentation-only changes,
Create scopes based on your work area (Web Frontend/Web Backend/Mobile etc.).
Here is a list based on work area:
- Web Frontend - webfrontend,
- Web Backend - webbackend,
If your commit is general, or type is specifying your work, then no scope is needed.
Please let us know about it via bug report on Binder's project repo.