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 or change the docker-library repository, please create an issue first. This way we can ensure that your precious work is not in vain.
Bug report flow as following:
Feature request flow as following:
If you want to start to develop this repository, it is very useful for you to read the develop documentation
Contributor only allow to fork main branch and pull request for it. Maintainers don't accept any pr to production branch
This repository have these branchs:
- Contributor's branch: Develpoer can fork main branch as their delelopment branch anytime
- main branch: The only branch that accepts PR from Contributors's branch
Flow: Contributor's branch → main branch
Pull request let you tell others about changes you've pushed to a branch in a repository on GitHub.
- Contributor commit to main branch
- pull request reviews
- Merge RP and CI/CD for it
DevOps thinks the same way 5m1e for manufacturing companies
We follow the development principle of minimization, rapid release
Use [major].[minor].[patch] for version serial number and version.json for version dependencies
Websoft9 use below Artifact for different usage:
- Dockerhub for image: Access Websoft9 docker images on Dockerhub
- Azure Storage for files: Access packages list at Azure Storage
- Type tags: Bug, enhancement, Documetation
- Stages Tags: PRD, Dev, QA(include deployment), Documentation
Websoft9 use the Github flow for development collaboration
See the LICENSE file for our project's licensing. We will ask you to confirm the licensing of your contribution.
We may ask you to sign a Contributor License Agreement (CLA) for larger changes.