diff options
| author | Colin Okay <okay@toyful.space> | 2022-03-14 08:21:12 -0500 |
|---|---|---|
| committer | Colin Okay <okay@toyful.space> | 2022-03-14 08:21:12 -0500 |
| commit | e2091250cbc8dce679b52636647949d0b417e6be (patch) | |
| tree | a7ba052808a2b284b99db30a78d392401b744bba /CONTRIBUTING.org | |
| parent | 86f7cdb2ce0f99aee0328617999f35b63694b4a6 (diff) | |
CONTRIBUTING rewording
Diffstat (limited to 'CONTRIBUTING.org')
| -rw-r--r-- | CONTRIBUTING.org | 15 |
1 files changed, 10 insertions, 5 deletions
diff --git a/CONTRIBUTING.org b/CONTRIBUTING.org index 9d896ee..2641f74 100644 --- a/CONTRIBUTING.org +++ b/CONTRIBUTING.org @@ -26,15 +26,20 @@ by starting the subject line with one of the following: - [PATCH vN] For patches (use git send-email) - [GENERAL CLI] For anything else -** Branch based collaboration +ADDITIONALLY, you may post general issues and bugreports here: +https://todo.sr.ht/~cbeo/oneliners.wiki + +** Making code contributions If you want to work on a feature, please make a new branch based on the relevant release candidate branch and develop your features there. -If the maintainer (me, Colin) has access to your git repo, simply -request that your branch be merged into the relevant release candidate -branch via the mailing list. +If the maintainer (me, Colin) has access to your git repo, use the +mailing list to request that your branch be merged into the relevant +release candidate branch. -Otherwise submit a patch against the release candidate branch. +If requesting a merge is infeasible because your git repository is +private or local to your machine, you may submit a patch against the +relevant release candidate branch via the mailing list. |