• Code of Conduct
• Asking Questions
• Opening an Issue
  • Reporting Security Issues
  • Bug Reports and Other Issues
• Feature Requests
• Triaging Issues
• Submitting Pull Requests
• Writing Commit Messages
  • Commit Structural Elements
    • Types
    • Scopes
    • Footers
• Example Commits
• Benefits of Conventional Commits
• Code Review
• Coding Style
• Certificate of Origin
• Credits

This guide serves to set clear expectations for everyone involved with the project so that we can improve it together while also creating a welcoming space for everyone to participate. Following these guidelines will help ensure a positive experience for contributors and maintainers.

Please review our Code of Conduct. It is in effect at all times. We expect it to be honored by everyone who contributes to this project. Acting like an asshole will not be tolerated.

See our Support Guide. In short, GitHub issues are not the appropriate place to debug your specific project, but should be reserved for filing bugs and feature requests.

Note: See the organization's default issue labels for reference and usage.

Before creating an issue, check if you are using the latest version of the project. If you are not up-to-date, see if updating fixes your issue first.

Review our Security Policy. Do not file a public issue for security vulnerabilities.

A great way to contribute to the project is to send a detailed issue when you encounter a problem. We always appreciate a well-written, thorough bug report. ✌️

In short, since you are most likely a developer, provide a ticket that you would like to receive.

• Review the documentation and Support Guide before opening a new issue.

• Do not open a duplicate issue! Search through existing issues to see if your issue has previously been reported. If your issue exists, comment with any additional information you have. You may simply note "I have this problem too", which helps prioritize the most common problems and requests.

• Prefer using reactions, not comments, if you simply want to "+1" an existing issue.

• Fully complete the provided issue template. The bug report template requests all the information we need to quickly and efficiently address your issue. Be clear, concise, and descriptive. Provide as much information as you can, including steps to reproduce, stack traces, compiler errors, library versions, OS versions, and screenshots (if applicable).

• Use GitHub-flavored Markdown. Especially put code blocks and console outputs in backticks (```). This improves readability.

Feature requests are welcome! While we will consider all requests, we cannot guarantee your request will be accepted. We want to avoid feature creep. Your idea may be great, but also out-of-scope for the project. If accepted, we cannot make any commitments regarding the timeline for implementation and release. However, you are welcome to submit a pull request to help!

• Do not open a duplicate feature request. Search for existing feature requests first. If you find your feature (or one very similar) previously requested, comment on that issue.

• Fully complete the provided issue template. The feature request template asks for all necessary information for us to begin a productive conversation.

• Be precise about the proposed outcome of the feature and how it relates to existing features. Include implementation details if possible.

You can triage issues which may include reproducing bug reports or asking for additional information, such as version numbers or reproduction instructions. Any help you can provide to quickly resolve an issue is very much appreciated!

We love pull requests! Before forking the repo and creating a pull request for non-trivial changes, it is usually best to first open an issue to discuss the changes, or discuss your intended approach for solving the problem in the comments for an existing issue.

For most contributions, after your first pull request is accepted and merged, you will be invited to the project and given push access. 🎉

Note: All contributions will be licensed under the project's license.

• Smaller is better. Submit one pull request per bug fix or feature. A pull request should contain isolated changes pertaining to a single bug fix or feature implementation. Do not refactor or reformat code that is unrelated to your change. It is better to submit many small pull requests rather than a single large one. Enormous pull requests will take enormous amounts of time to review, or may be rejected altogether.

• Coordinate bigger changes. For large and non-trivial changes, open an issue to discuss a strategy with the maintainers. Otherwise, you risk doing a lot of work for nothing!

• Prioritize understanding over cleverness. Write code clearly and concisely. Remember that source code usually gets written once and read often. Ensure the code is clear to the reader. The purpose and logic should be obvious to a reasonably skilled developer, otherwise you should add a comment that explains it.

• Follow existing coding style and conventions. Keep your code consistent with the style, formatting, and conventions in the rest of the code base. When possible, these will be enforced with a linter. Consistency makes it easier to review and modify in the future.

• Include test coverage. Add unit tests or UI tests when possible. Follow existing patterns for implementing tests.

• Update the example project if one exists to exercise any new functionality you have added.

• Add documentation. Document your changes with code doc comments or in existing guides.

• Update the CHANGELOG for all enhancements and bug fixes. Include the corresponding issue number if one exists, and your GitHub username. (example: "bug: fixed crash in profile view resolving #123 @johndoe")

• Use the repo's default branch. Branch from and submit your pull request to the repo's default branch. Usually this is main, but it could be dev, develop, or master.

• Resolve any merge conflicts that occur.

• Promptly address any CI failures. If your pull request fails to build or pass tests, please push another commit to fix it.

• When writing comments, use properly constructed sentences, including punctuation.

• Use spaces, not tabs.

Please write a great commit message, ideally following the conventional commits framework:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Note: Commit types fall inline with most of the pre-specified, default issue labels: feat: , bug:, docs:, chore:, etc.

• feat: - feature or enhancement
  • Typically tied to a pre-existing issue or pull request that should be referenced in the commit message or body
  • Keep feature commits atomic and specific
• bug: or fix: - bugs, patches, hot-fixes, defects, etc.
  • Correlates with the PATCH number in Semantic Versioning (i.e. MAJOR.MINOR.PATCH)

other potential types:

• devops: (CI/CD)
  • Related to continuous integration or deployment (i.e. GitHub Actions or external pipelines).
• test:
  • Testing related commits (also includes any code-coverage associated with the test being committed)
  • Unit, integration, end-to-end, functional, regression, etc.
• docs:
  • Documentation related
• setup:
  • Initialization and setup of the repository
• infra:
  • Infrastructure related (i.e. Terraform, Ansible, Vagrant, Azure Bicep, Azure Resource Management Templates, AWS Cloud Formation, etc.) and associated scripts for infrastructure.
• release:
  • Commits specific to releases
  • These commits should be tagged and annotated with the corresponding release version.
  • Additionally, a release checklist issue can be linked to in the commit body or message for reference.
• refactor: or cleanup:
  • Code refactorings and cleanup commits (non-breaking)
• chore:
  • Chores typically made by non-human interactions with the repo
• style:
  • Code Style changes or proposals

Other commit types are allowed but try to follow a specific taxonomy for clarity amongst other developers.

See commitlint/config-conventional and the Angular conventions for reference and guidelines.

Scopes are optional and follow the syntax elaborated above in the commit message (<type>[optional scope]: <description>). Scopes represent additiona contextual information and should be contained within parenthesis, for example, feat(api): add new endpoint for user authentication represents a feature commit under the scope of the API component of the project.

• BREAKING CHANGE: a commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in Semantic Versioning). A BREAKING CHANGE can be part of commits of any type.

Footers other than BREAKING CHANGE: <description> are acceptable and may be provided by following a convention similar to the git trailer format.

feat: update function XYZ with new arguments to support new business logic

BREAKING CHANGE: argument `A` was removed in support for argument `B`.

feat!: add functionality for sending emails to user when new product is available

feat(api)!: add functionality for sending emails to user when new product is available

• Automatically generating CHANGELOGs and RELEASE NOTES (for example see git-cliff).
• Automatically determining a semantic version bump (based on the types of commits landed).
• Communicating the nature of changes to teammates, the public, and other stakeholders.
• Triggering build and publish processes.
• Making it easier for people to contribute to your projects, by allowing them to explore a more structured commit history.

1. Separate subject from body with a blank line
2. Limit the subject line to 50 characters
3. Capitalize the subject line
4. Do not end the subject line with a period
5. Use the imperative mood in the subject line (example: "Fix networking issue")
6. Wrap the body at about 72 characters
7. Use the body to explain why, not what and how (the code shows that!)
8. If applicable, prefix the title with the relevant component name. (examples: "[Docs] Fix typo", "[Profile] Fix missing avatar")

[TAG] Short summary of changes in 50 chars or less

Add a more detailed explanation here, if necessary. Possibly give 
some background about the issue being fixed, etc. The body of the 
commit message can be several paragraphs. Further paragraphs come 
after blank lines and please do proper word-wrap.

Wrap it to about 72 characters or so. In some contexts, 
the first line is treated as the subject of the commit and the 
rest of the text as the body. The blank line separating the summary 
from the body is critical (unless you omit the body entirely); 
various tools like `log`, `shortlog` and `rebase` can get confused 
if you run the two together.

Explain the problem that this commit is solving. Focus on why you
are making this change as opposed to how or what. The code explains 
how or what. Reviewers and your future self can read the patch, 
but might not understand why a particular solution was implemented.
Are there side effects or other unintuitive consequences of this
change? Here's the place to explain them.

 - Bullet points are okay, too

 - A hyphen or asterisk should be used for the bullet, preceded
   by a single space, with blank lines in between

Note the fixed or relevant GitHub issues at the end:

Resolves: #123
See also: #456, #789

• Review the code, not the author. Look for and suggest improvements without disparaging or insulting the author. Provide actionable feedback and explain your reasoning.

• You are not your code. When your code is critiqued, questioned, or constructively criticized, remember that you are not your code. Do not take code review personally.

• Always do your best. No one writes bugs on purpose. Do your best, and learn from your mistakes.

• Kindly note any violations to the guidelines specified in this document.

Consistency is the most important. Following the existing style, formatting, and naming conventions of the file you are modifying and of the overall project. Failure to do so will result in a prolonged review process that has to focus on updating the superficial aspects of your code, rather than improving its functionality and performance.

For example, if all private properties are prefixed with an underscore _, then new ones you add should be prefixed in the same way. Or, if methods are named using camelcase, like thisIsMyNewMethod, then do not diverge from that by writing this_is_my_new_method. You get the idea. If in doubt, please ask or search the codebase for something similar.

When possible, style and format will be enforced with a linter.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

1. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or
2. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or
3. The contribution was provided directly to me by some other person who certified (1), (2) or (3) and I have not modified it.
4. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

If you are reading this, bravo dear user and (hopefully) contributor for making it this far! You are awesome. 💯

To confirm that you have read this guide and are following it as best as possible, include this emoji at the top of your issue or pull request: 🖤

Please feel free to adopt this guide in your own projects. Fork it wholesale or remix it for your needs.

Many of the ideas and prose for the statements in this document were based on or inspired by work from the following communities:

• Alamofire
• CocoaPods
• Docker
• Linux

We commend them for their efforts to facilitate collaboration in their projects.