Mirror of @tangled.org/core. Running on a Raspberry Pi Zero 2 (Please be gentle).
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

docs/contributing.md: reword nested dirs & general notes

Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.sh>

+7 -3
+7 -3
docs/contributing.md
··· 33 33 knotserver: git/service: improve error checking in upload-pack 34 34 ``` 35 35 36 - The affected package/directory can be truncated down to just the relevant dir 37 - should it be far too long. For example `pages/templates/repo/fragments` can 38 - simply be `repo/fragments`. 39 36 40 37 ### general notes 41 38 ··· 40 43 using `git am`. At present, there is no squashing -- so please author 41 44 your commits as they would appear on `master`, following the above 42 45 guidelines. 46 + - If there is a lot of nesting, for example "appview: 47 + pages/templates/repo/fragments: ...", these can be truncated down to 48 + just "appview: repo/fragments: ...". If the change affects a lot of 49 + subdirectories, you may abbreviate to just the top-level names, e.g. 50 + "appview: ..." or "knotserver: ...". 51 + - Keep commits lowercased with no trailing period. 43 52 - Use the imperative mood in the summary line (e.g., "fix bug" not 44 53 "fixed bug" or "fixes bug"). 45 54 - Try to keep the summary line under 72 characters, but we aren't too 46 55 fussed about this. 56 + - Follow the same formatting for PR titles if filled manually. 47 57 - Don't include unrelated changes in the same commit. 48 58 - Avoid noisy commit messages like "wip" or "final fix"—rewrite history 49 59 before submitting if necessary.