Lines Matching +full:docs +full:- +full:review
4 <!---
5 Please use a pull request to the appropriate branch ('release' for backward-compatible bug fixes fo…
6 -->
7 …e your commits well-organized and [atomic](https://en.wikipedia.org/wiki/Atomic_commit#Atomic_comm…
12 …efficiency of reviewing and facilitates use of [`git bisect`](https://git-scm.com/docs/git-bisect).
15 It is useful to create a WIP (work in progress) pull request for any long-running development so th…
20 …-by: Helpful User <helpful@example.com>` or [`Co-authored-by: Snippet Mentor <code.by@comment.com>…
22 If your author information or email becomes inconsistent (look at `git shortlog -se`), please edit …
24 … and support it, their names are included in the automatically generated user-manual documentation.
43 …tion (including all personal information I submit with it, including my sign-off) is maintained in…
48 …ntributors receive appropriate recognition through informal and academically-recognized credit sys…
51 …cant contributions to HONEE (in implementation, documentation, conceptualization, review, etc.) and
56 Authors of publications about HONEE as a whole, including DOI-bearing archives, shall offer co-auth…
57 …ic HONEE contributions shall evaluate those listed in `AUTHORS` and offer co-authorship to those w…
59 Note that there is no co-authorship expectation for those publishing about use of HONEE (versus cre…