How to contribute
This document provides information on how to contribute to Pan-Net DevOps documentation.
This web resource was born as an aggregation of our experience in managing the application lifecycle with CI/CD. But not only. Our goal is to bring together like-minded people interested in modern methods of Development, Deployment and Operations of Cloud Applications. To encourage the exchange of knowledge within the community and find the best tools and approaches to meet the challenges. Therefore, we highly welcome any feedback, comments and contribution.
If you have an idea how to improve this documentation, there are two ways to do it:
- Use the feedback form. We will process your request, create an issue, if needed, and inform you about the progress.
- Use the instruction below to make changes yourself
General contribution flow
The general flow for contributing to the Pan-Net DevOps repository is:
- Request access to the project using the link on the top of the project overview page and wait for access to be granted.
- Choose a topic to work on.
- Open an issue in Gitlab.
- Assign yourself to the issue.
- Create a brunch using a drop-down menu in front of the
Create merge request
button. Pls, choose branchdevelop
as a source. This will automatically create a branch with the issue number and title as branch name e.g. : 1-example-issue. - Work on the feature. You can use staging repository when you want to test changes online.
- Open Merge Request to
develop
branch. Squashing commits is recommended. - Maintainer will review your MR and approve merge to
develop
branch. - Maintainer will create MR and merge
develop
branch tomaster
.
Recommendations
When adding or reviewing new topics make sure you:
- Write a clear, short, and on point sentences
- Visually differentiate code snippets so the user can copy/paste them
- Include all dependencies and prerequisites user might need for your example to work
- Test your code snippets on a vanilla system
Licensing
The Pan-Net DevOps documentation is available under the Creative Commons Share-Alike 4.0 International (CC BY-SA 4.0). This license allows us to ensure that this knowledge remains free and open while encouraging contribution and authorship.
For more information regarding the license and its usage please go here: https://creativecommons.org/licenses/by-sa/4.0/