erabo/spiegel_podman
1
0
Fork 0
mirror of https://github.com/podman-container-tools/podman.git synced 2026-08-18 22:37:52 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Merge pull request #25313 from baude/pronlymain

Browse source 
Update CONTRIBUTING for main branch
This commit is contained in:
openshift-merge-bot[bot] 2025-02-17 20:55:30 +00:00 • committed by GitHub
commit df6070f8d7
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
CONTRIBUTING.md
View file

@ -185,6 +185,10 @@ PRs for new features should include some background on what use cases the new co
When possible and when it makes sense, try to break-up larger PRs into smaller ones - it's easier to review smaller code changes.
But only if those smaller ones make sense as stand-alone PRs.
Pull requests should be submitted to the main branch of the Podman repository. Bug fixes may be cherry-picked or back-ported
to Podman release branches but must first be merged upstream. Maintainers reserve the right to not accept any pull requests
to any release branches.
Regardless of the type of PR, all PRs should include:
* Well-documented code changes, both through comments in the code itself and high-quality commit messages.
* Additional tests. Ideally, they should fail w/o your code change applied.