Skip to content

Latest commit

 

History

History
46 lines (35 loc) · 1.79 KB

CONTRIBUTING.md

File metadata and controls

46 lines (35 loc) · 1.79 KB

Contributing

Submitting Changes

  1. Fork the repository
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Execute the unit tests to ensure all pass
  5. Squash your commits (git rebase --interactive --autosquash)
  6. Push the branch (git push origin my-new-feature)
  7. Create a new Pull Request

Pull request Approval

Internal developers will verify the changes and approve the request or leave comments for improvements.

Quality Expectations

Please ensure any contributions include unit tests. The project maintains a high level of test coverage for its functionality. Submissions are expected to maintain a similar level of coverage.

Code of Conduct

Examples of behavior that contributes to creating a positive environment include:

  • Using welcoming and inclusive language
  • Being respectful of differing viewpoints and experiences
  • Gracefully accepting constructive criticism
  • Focusing on what is best for the community
  • Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

  • The use of sexualized language or imagery and unwelcome sexual attention or advances
  • Trolling, insulting/derogatory comments, and personal or political attacks
  • Public or private harassment
  • Publishing others' private information, such as a physical or electronic address, without explicit permission
  • Other conduct which could reasonably be considered inappropriate in a professional setting

How to engage Maintainers

Leaving Issues using the issue tracker in GitHub. Maintainers will look for issues posted to the repository and will resolve the issue as soon as possible.

Copyright © 1994-2022, All Rights Reserved by Mastercard.