From cf6dd2c310deae2e655d372f6b1f2f20290c7e3c Mon Sep 17 00:00:00 2001 From: s1d3sw1ped_bot Date: Tue, 1 Sep 2026 19:00:20 +0000 Subject: [PATCH] docs: Align CONTRIBUTING.md with develop main and develop carried different CONTRIBUTING.md blobs after parallel docs landings. Replace the main copy with the develop tip content so both branches share one guide. --- CONTRIBUTING.md | 36 ------------------------------------ 1 file changed, 36 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 9560597..e69de29 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,36 +0,0 @@ -# Contributing - -## Pull requests - -Prefer pull requests against `develop`. The repository default is `master` -or `main`; `develop` exists for ongoing integration. - -## Commits - -Subject form (kernel-style): - - area: Imperative summary - -- Imperative mood after the colon (`Add`, `Fix`, `Remove`, …). -- No trailing period on the subject. Aim for about 75 characters total. -- Body states the problem and why the change is right. -- One logical change per commit. Skip the body only when the subject alone - is obvious to a reviewer. - -## Pull request description - -- **What** — what changed -- **Why** — problem and impact -- **Test** — concrete steps a reviewer can run - -Do not leave the description as “see commits”. - -## Issues - -Gitea closes issues when a bare issue reference appears in merge text. -Cite leftover issues by full URL. Only close an issue when the merge -actually finishes that work. - -## License - -License: see LICENSE if present; otherwise TBD by owner.