ahuston-0/nix-dotfiles
1
0
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases Wiki Activity

fix list alignment

Browse Source 
Signed-off-by: ahuston-0 <aliceghuston@gmail.com>
This commit is contained in:
ahuston-0 2024-07-07 19:00:43 -04:00 committed by Alice Huston
parent 9eb9379b5c
commit 2e6cfb42af
1 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
docs/CONTRIBUTING.md
View File

@ -69,12 +69,12 @@ which do not have an associated issue must be tagged to the same. It is
**highly recommended** that all PR's be tagged to an issue but PR's should **highly recommended** that all PR's be tagged to an issue but PR's should
not be rejected if they are not tagged to an issue. not be rejected if they are not tagged to an issue.
Any issue or PR that is tagged to the project must have a priority (High/Medium Any issue or PR that is tagged to the project must have a priority
/Low) and an estimate (rough amount of time in hours) associated. Start date (High/Medium/Low) and an estimate (rough amount of time in hours) associated.
and end date must be included for non-critical items (branches not beginning Start dateand end date must be included for non-critical items (branches not
with `hotfix/` or `urgent/`). This is done in order to understand effort and beginning with `hotfix/` or `urgent/`). This is done in order to understand
criticality of the project item. Please see [Critical Issues](#critical-issues) effort and criticality of the project item. Please see
for further details. [Critical Issues](#critical-issues) for further details.
### Critical Issues ### Critical Issues
@ -87,13 +87,13 @@ rules.
- Critical issues may bypass the [quorum rules](#review-process), as long as the - Critical issues may bypass the [quorum rules](#review-process), as long as the
PR has been tested on at least one machine PR has been tested on at least one machine
- Issues which bypass the quorum process must have a second reviewer tagged - Issues which bypass the quorum process must have a second reviewer tagged
- All critical issues which bypass the approval process must have an RCA issue - All critical issues which bypass the approval process must have an RCA issue
opened and the RCA logged into the `inc/` folder opened and the RCA logged into the `inc/` folder
- The second reviewer has 2 weeks to retroactively review and approve the PR - The second reviewer has 2 weeks to retroactively review and approve the PR
- If the retro does not happen in the given window, an issue shall be opened - If the retro does not happen in the given window, an issue shall be opened
to either re-review the PR or to revert and replace the fix with a to either re-review the PR or to revert and replace the fix with a
permanent solution permanent solution
- Critical issues must be tagged to `Nix Flake Features` project, and must have - Critical issues must be tagged to `Nix Flake Features` project, and must have
a priority of `High` and an estimate tagged. Start and end date are not needed a priority of `High` and an estimate tagged. Start and end date are not needed