Skip to content
This repository has been archived by the owner on Mar 23, 2024. It is now read-only.

Latest commit

 

History

History
67 lines (38 loc) · 3.66 KB

CONTRIBUTING.md

File metadata and controls

67 lines (38 loc) · 3.66 KB

Contributing

From opening a bug report to creating a pull request: every contribution is appreciated and welcome. If you're planning to:

  • implement a new feature please start a discussion in the idea category first
  • fix a bug, please create an issue first

This way we can ensure that your precious work is not in vain.

Not Sure Where to Start?

If you want to participate to this project, but you are not sure how you can do it, do not hesitate to contact @rpothin:

How the repository is organized

At a high level, here are the main folders of this repository:

  • .github/workflows - contains all the GitHub workflows available in this repository and that can be use to manage the ALM process of Power Platform solutions directly from GitHub.
  • Scripts - contains PowerShell scripts consumed by the GitHub workflows.

Contributing to this project

  • Please maintain the existing code style.

  • Please try to keep your commits small and focused.

  • Please test your work.

  • If the project diverges from your branch, please rebase instead of merging. This makes the commit graph easier to read.

  • Once your work is completed, please raise a PR against the main branch with some information about what has changed and why.

Getting Started For Contributors

You can explore this repository and fork it at any time, but if you want to submit changes you will need to link your pull request to an existing issue.

1. Fork this repository

If you do not know how to do this, you can follow the Fork a repo page of the GitHub documentation.

2. Create a new branch

In your fork repository create a new branch to make your changes. If you need guidance for this part, GitHub has a good page about Creating a branch in its documentation.

3. Do your changes

Do whatever changes you want in your new branch in your forked repository.

4. Test your changes

Do not forget to test your changes. We want to catch possible issues as soon as possible (before it reaches the main repository) in the change process.

5. Submit your changes with a pull request

The last step concist to submit your changes with a pull request. Once again, there is a great page about Creating a pull request from a fork in the GitHub documentation.

Other Useful Information