Skip to content

Latest commit

 

History

History
44 lines (32 loc) · 2.48 KB

Contributing.md

File metadata and controls

44 lines (32 loc) · 2.48 KB

Contributing

Code of conduct

Please review the Code of Conduct for this project.

Contribution model

All contributions to this project should be through pull requests (PR) against the main branch.

Before you start, make sure you have read the Git branch setup instructions.

Creating a pull request

If you are new to Git, read more about creating a pull request.

Project specific PR guidelines:

  • Before creating a PR, please be sure to verify the scenarios to test before creating a PR.
  • If your PR involves UI work, please include a screenshot of the relevant changes in the PR description / as a PR comment.
  • Every PR that is created will kick off a build. Be sure to verify that the build for your PR has passed. The status of the build along with the status of any other checks will be displayed at the bottom of a PR.
  • Address any build failures on the PR. To get more information about build failures:
    • Click on "Show all checks" at the bottom of a PR.
    • Click on "Details" for the PR build.
    • Click on the build in the left pane. This should display the information associated with that build.
    • For more details, click on "View more details on Azure Pipelines".

Contributing license agreement

This project welcomes contributions and suggestions. Most contributions require you to agree to a contributor license agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

Bugs

We use github issues to track bugs.

See something wrong / that can be improved upon? Visit the issues page to see if an issue for it already exists.

If it doesn't, feel free to file an issue.

FAQ

Please visit our FAQ section to get answers to common questions.