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.

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

SMA-0: Update CONTRIBUTING.md #1

Merged
merged 1 commit into from
Jan 20, 2024
Merged
Changes from all commits
Commits
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
6 changes: 3 additions & 3 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,8 @@
## Workflow

1. Create a feature branch when you start to work on a story and commit your changes to this
- the branch should be named `<id of the ticket>: <subject>`, for example `TB-3: Add login endpoint`
- the commits should also be named `<id of the ticket>: <subject>`, for example `TB-3: added unit tests`
- the branch should be named `<id of the ticket>: <subject>`, for example `SMA 3 Add login endpoint`
- the commits should also be named `<id of the ticket>: <subject>`, for example `SMA 3 added unit tests`
2. Push this frequently to the remote repository from your local
2. When the feature is done, create a Pull Request from the `feature_branch` to `development`, follow the guidelines
3. When the PR is approved, merge it, and delete your feature branch
Expand All @@ -19,7 +19,7 @@ Read this article how to write meaningful commit messages:
[How to Write a Git Commit Message](https://chris.beams.io/posts/git-commit/)

We follow the rules below:
- **Commit message format**: `TB-{id}: <subject>`
- **Commit message format**: `SMA {id} <subject>`
- **id**: Id of the ticket you are working on (in jira)
- **Subject**: Changes in the commit

Expand Down