~ruther/guix-local

321edcf0744a8895690579e8a5b09b66c75d102c — Christopher Baines 1 year, 6 months ago ddbb59f
doc: contributing: Add guidance on reverting commits.

Particularly to cover the case where things might need to happen with the
build farms if changes are reverted.

* doc/contributing.texi (Commit Access): Add guidance on reverting commits.

Change-Id: Iba320b76b0927b693c75054b5473a50bdd77c7ee
1 files changed, 14 insertions(+), 0 deletions(-)

M doc/contributing.texi
M doc/contributing.texi => doc/contributing.texi +14 -0
@@ 2945,6 2945,20 @@ implicitly blame them, which is unhelpful.  Accountability comes from
a consensus about the problem, learning from it and improving
processes so that it's less likely to reoccur.

@subsubsection Reverting commits

Like normal commits, the commit message should state why the changes are
being made, which in this case would be why the commits are being
reverted.

If the changes are being reverted because they led to excessive number
of packages being affected, then a decision should be made whether to
allow the build farms to build the changes, or whether to avoid
this. For the bordeaux build farm, commits can be ignored by adding them
to the @code{ignore-commits} list in the
@code{build-from-guix-data-service} record, found in the bayfront
machine configuration.

@subsection Commit Revocation

In order to reduce the possibility of mistakes, committers will have