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

470 # Add instructions for contributors #1134

Merged
merged 1 commit into from
Oct 25, 2022
+7 −0
Merged

470 # Add instructions for contributors #1134

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
7 changes: 7 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,13 @@ From the root directory of your local Passage git-repository clone run the follo

## Commits

### Ticket reference

Each commit contributes a code improvement in landscape of a certain situation.
Whether it is a bug, a new functionality, an extension, some refactoring or else, there must be a ticket (issue) which states the reason for the commit(s), contains discussions and all the information necessary to trace the commit origin.

It can be one of [existing](https://github.com/eclipse-passage/passage/issues) or [new one, created by you](https://github.com/eclipse-passage/passage/issues/new), but it is mandatory to have a ticket for any commit.

### Message Guidelines

Start with `Bug: <record>` stating the Bugzilla record number the change is related to; to reference a GiHub issue start with `Bug: #<issue>`
Expand Down