remote/open-slopware
1
0
Fork 0
mirror of https://codeberg.org/small-hack/open-slopware.git synced 2026-06-05 16:47:00 +02:00
Code Issues Projects Releases Packages Wiki Activity

Add note to please create individual PRs and Issues to avoid large merge conflicts and confusion

Browse source
This commit is contained in:
jessebot 2026-03-17 13:15:48 +01:00
commit 915ad679b6
1 changed files with 5 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

6
CONTRIBUTING.md
View file

@ -5,6 +5,8 @@ To contribute to this list, file a pull request adding it to the appropriate cat
> [!WARNING]
> Please do your best to *research alternatives* to the slopware before submitting a PR. It's important to elevate projects that aren't drinking the slop <3
Please make sure to only submit a PR for 1 piece of software or section at a time, otherwise it more difficult to coordinate between multiple Issues and PRs.
### Criteria
The criteria for being included in this repository are any of:
@ -22,4 +24,6 @@ Any project here may be removed as long as the following become true, *even if p
## Issues
Issues are meant primarily for discussing if something should be added or questions regarding clarification. An issue that says "Add x software" will be treated as a call to community action and labeled with `ready-for-pr` provided it meets the above criteria. This is not a problem, but does not necessarily mean the core maintainers of this repo will create that PR for you, however it does mean you or someone else in the community is clear to go ahead and submit a PR for that software. This is maintained in the community's free time, so please understand that there will sometimes be a delay in when a PR is generated for you.
Issues are meant primarily for discussing if something should be added or questions regarding clarification. An issue that says "Add x software" will be treated as a call to community action and labeled with `ready-for-pr` provided it meets the above criteria. This is not a problem, but does not necessarily mean the core maintainers of this repo will create that PR for you, however it does mean you or someone else in the community is clear to go ahead and submit a PR for that software. This is maintained in the community's free time, so please understand that there will sometimes be a delay in when a PR is generated for you.
Please make sure to only submit an Issue for 1 piece of software or section at a time, otherwise it more difficult to coordinate between multiple Issues and PRs.