1 |
Update the description for --bug and --closes to account for the fact |
2 |
that the tags are now handled by git hooks on Gentoo Infra, and cause |
3 |
actions on Gentoo Bugzilla. |
4 |
|
5 |
// NB: It would probably make sense for --closes to default to Gentoo |
6 |
bug numbers now. However, I have doubts that some people might have |
7 |
already started using it for pull requests, and that might cause |
8 |
confusion. What do you think? |
9 |
--- |
10 |
repoman/man/repoman.1 | 11 +++++++---- |
11 |
1 file changed, 7 insertions(+), 4 deletions(-) |
12 |
|
13 |
diff --git a/repoman/man/repoman.1 b/repoman/man/repoman.1 |
14 |
index a49c72c0d..4b518e6f1 100644 |
15 |
--- a/repoman/man/repoman.1 |
16 |
+++ b/repoman/man/repoman.1 |
17 |
@@ -27,13 +27,16 @@ be either a Gentoo bug number or a full bug URL (either Gentoo |
18 |
or upstream). Gentoo bug URLs are automatically shortened to |
19 |
the canonical \fBhttps://bugs.gentoo.org/NNNNNN\fR form, and HTTPS |
20 |
is forced for known bug trackers. |
21 |
+ |
22 |
+When pushing to the Gentoo repository, the reference to the commit |
23 |
+will be automatically added as a comment on the bug. |
24 |
.TP |
25 |
\fB-c\fR, \fB--closes\fR |
26 |
Include a \fBCloses\fR tag in the commit message footer that can be used |
27 |
-to close pull requests (and issues) on GitHub and other compatible |
28 |
-services (GitLab, Bitbucket). The argument can be either a PR number for |
29 |
-the gentoo/gentoo GitHub repository or a full PR/bug URL. For bug URLs, |
30 |
-HTTPS is forced automatically for known bug/PR trackers. |
31 |
+to close bugs and pull requests (e.g. on Gentoo Bugzilla, GitHub, GitLab, |
32 |
+Bitbucket). The argument can be either a PR number for the gentoo/gentoo |
33 |
+GitHub repository or a full PR/bug URL. For bug URLs, HTTPS is forced |
34 |
+automatically for known bug/PR trackers. |
35 |
.TP |
36 |
\fB\-\-digest=<y|n>\fR |
37 |
Automatically update Manifest digests for modified files. This |
38 |
-- |
39 |
2.14.1 |