Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix:Update CONTRIBUTING.md #863

Merged
merged 2 commits into from
Feb 16, 2024
Merged

fix:Update CONTRIBUTING.md #863

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
22895d8
fix:Update CONTRIBUTING.md
thrbnhrtmnn Feb 1, 2024
b708b9b
Merge branch 'develop' into fix/372-update-branch-naming-convention
thrbnhrtmnn Feb 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,7 +130,7 @@ For contributions we are using [Gitflow as branching strategy](https://www.atlas
The branch name should not exceed a maximum character count of 140. Each branch should follow the following structure:
`<branchType>/<issueNumber>_<summary>`

- **branchType:** As defined in the Gitflow branching strategy, there are different types of branches. The allowed types are: `release`, `hotfix` and `feature`. 

- **branchType:** As defined in the Gitflow branching strategy, there are different types of branches. Besides the existing `main` and `develop` branches, the allowed types for newly created branches are: `release`, `hotfix`, `feature` and `fix`. The branch type `fix` is not defined in Gitflow, but is used exactly like a `feature` branch. It was added to be more granular in our naming convention and to differentiate between branches that implement something new (`feature`) and those that change something that already exists (`fix`).
- **issueNumber:** The issue number of your task. For example: `421`

- **summary:** A few words describing the issue. When there are multiple words, you can use a hyphen to link the words. For example: `text-area-storybook-documentation` 


Expand Down
Loading