maurice/snix
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(REVIEWS): link additional related documentation

Browse source 
Unfortunately, the git book doesn't link the man pages of the involved
tools, but I assume users will figure out to read them on their own.
I've not linked https://git-send-email.io due to the slight reservation
that it's not an official resource (and is an advertisment), but I don't
feel strongly on that. The linked chapter of the Git Book links it in a
footnote anyways.

Change-Id: I70e3c75396006256c775f84bc7aeb5a4bde081a1
Reviewed-on: https://cl.tvl.fyi/c/depot/+/13032
Tested-by: BuildkiteCI
Reviewed-by: tazjin <tazjin@tvl.su>
Autosubmit: sterni <sternenseemann@systemli.org>
This commit is contained in:
sterni 2025-01-21 15:21:00 +01:00 • committed by clbot
parent e102e6686b
commit 58cafde03d
1 changed files with 7 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/REVIEWS.md
View file

@ -103,7 +103,9 @@ git push origin HEAD:refs/for/canon%wip
TIP: Every individual commit will become a separate change. We do not squash TIP: Every individual commit will become a separate change. We do not squash
related commits, but instead submit them one by one. Be aware that if you are related commits, but instead submit them one by one. Be aware that if you are
expecting a different behaviour and attempt something like an unsquashed subtree expecting a different behaviour and attempt something like an unsquashed subtree
merge, you will produce a *lot* of CLs. This is strongly discouraged. merge, you will produce a *lot* of CLs (read
[how to import another project properly][importing-projects]).
This is strongly discouraged.
During your review, the reviewer(s) might ask you to make changes. You can During your review, the reviewer(s) might ask you to make changes. You can
simply amend your commit(s) and push to the same ref. Gerrit will automatically simply amend your commit(s) and push to the same ref. Gerrit will automatically
@ -159,6 +161,8 @@ Create an appropriate commit locally and send it us using either of these option
* `git send-email`: If configured on your system, this will take care of the * `git send-email`: If configured on your system, this will take care of the
whole emailing process for you. whole emailing process for you.
For more details, refer to the [official git documentation][git-contributing-email].
The email address is a [public inbox][]. The email address is a [public inbox][].
## Gerrit for GitHub Users ## Gerrit for GitHub Users
@ -204,3 +208,5 @@ read.
[github-diff]: https://gerrit.wikimedia.org/r/Documentation/intro-gerrit-walkthrough-github.html [github-diff]: https://gerrit.wikimedia.org/r/Documentation/intro-gerrit-walkthrough-github.html
[attention sets]: https://gerrit-review.googlesource.com/Documentation/user-attention-set.html [attention sets]: https://gerrit-review.googlesource.com/Documentation/user-attention-set.html
[attention-set-rules]: https://gerrit-review.googlesource.com/Documentation/user-attention-set.html#_rules [attention-set-rules]: https://gerrit-review.googlesource.com/Documentation/user-attention-set.html#_rules
[git-contributing-email]: https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project#_project_over_email
[importing-projects]: ./importing-projects.md