Skip to content

Latest commit

 

History

History
59 lines (35 loc) · 2.51 KB

CONTRIBUTING.md

File metadata and controls

59 lines (35 loc) · 2.51 KB

Contributing

gopass uses GitHub to manage reviews of pull requests.

Steps to Contribute

Should you wish to work on an issue, please claim it first by commenting on the GitHub issue you want to work on it. This will prevent duplicated efforts from contributors.

Please check the help-wanted label to find issues that need help. If you have questions about one of the issues please comment on them and one of the maintainers will try to clarify it.

Pull Request Checklist

  • Use that latest stable Go release

  • Branch from master and, if needed, rebase to the current master branch before submitting your pull request. If it doesn't merge cleanly with master you will be asked to rebase your changes.

  • Commits should be as small as possible, while ensuring that each commit is correct independently.

  • Add tests relevant to the fixed bug or new feature.

  • Commit messages must contain Developer Certificate of Origin / Signed-off-by line, for example:

    One line description of commit
    
    More detailed description of commit, if needed.
    
    Signed-off-by: Your Name <[email protected]>
    
  • The first line of the commit message, the subject line, should be prefix with a tag indicating the type of the change. These tags will be extracted and used to populate the changelog. Valid [TAG]s are [BREAKING], [BUGFIX], [CLEANUP], [DEPRECATION], [DOCUMENTATION], [ENHANCEMENT], [FEATURE], [TESTING], and [UX].

Building & Testing

  • Build via go build to create the binary file ./gopass.
  • Run unit tests with: make test
  • Run meta tests with: make codequality
  • Run integration tests make test-integration

If any of the above don't work check out the troubleshooting section.

Releasing

See docs/releases.md.