Skip to content

Latest commit

 

History

History
45 lines (28 loc) · 1.75 KB

CONTRIBUTING.md

File metadata and controls

45 lines (28 loc) · 1.75 KB

Contributing to actix-permissions

Thanks for your interest and work in actix permissions.

Getting Started

Actix-permissions open issues are here. Issues can include bugs to fix, features to add, or documentation that looks outdated.

For some tips on contributing to open source, this post is helpful.

Contributions

Everyone is welcome to contribute.

Contributions should be made in the form of GitHub pull requests. Each pull request will be reviewed by a core contributor (someone with permission to land patches) and either landed in the main tree or given feedback for changes that would be required.

Pull Request Checklist

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

  • Commits should be as small as possible, while ensuring that each commit is correct independently (i.e., each commit should compile and pass tests).

  • Commit messages should be capitalized and short. For other recommendations on writing commit messages take a look at this helpful post.

  • Don't put submodule updates in your pull request unless they are to landed commits.

  • If your patch is not getting reviewed or you need a specific person to review it, you can @-reply a reviewer asking for a review in the pull request or a comment.

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

Conduct

We follow the Rust Code of Conduct.

All code in this repository is under the MIT/Apache-2.0.