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.
If you want to participate to this project, but you are not sure how you can do it, do not hesitate to contact @rpothin:
- By email at [email protected]
- On Twitter
At a high level, here are the main folders of this repository:
- .github/workflows - contains all the GitHub workflows available in this repository.
- infra - contains the infrastructure as code in Bicep.
- src/functionapp - contains the code of the C# Azure Functions app.
-
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.
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.
If you do not know how to do this, you can follow the Fork a repo page of the GitHub documentation.
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.
Do whatever changes you want in your new branch in your forked repository.
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.
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.
-
This project uses a MIT license.
-
We follow a CODE OF CONDUCT. Please read it.