Skip to content

Commit

Permalink
templates: Clarify how issue reference carry over can be prevented.
Browse files Browse the repository at this point in the history
  • Loading branch information
okurz committed Nov 3, 2023
1 parent 36c8ea4 commit cec372e
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions templates/webapi/comments/add_comment_form_groups.html.ep
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
</p>
<ul>
<li>
For bugreferences write <code><i>bugtracker_shortname</i>#<i>bug_nr</i></code> in a comment, e.g. <code>bsc#1234</code>.
For issue references write <code><i>bugtracker_shortname</i>#<i>bug_nr</i></code> in a comment, e.g. <code>bsc#1234</code> anywhere in a sentence
</li>
<li>
For generic labels use <code>label:<i>keyword</i></code> where <i>keyword</i> can be any valid character up to the next whitespace, e.g. "false_positive".
Expand All @@ -28,7 +28,8 @@
</p>
<p>
Issue references are automatically carried over to the next jobs in the same scenario when the corresponding job fails in
the same module or the failed modules did not change.
the same module or the failed modules did not change. To mention links to tickets without enabling them for carry-over you can prepend the
link or short-reference with <code>label:</code>, e.g. <code>this is *not* label:bsc#1234</code>.
</p>
<p>
Comments on job group pages can be "pinned" to the top by including the special keyword <code>pinned-description</code>
Expand Down

0 comments on commit cec372e

Please sign in to comment.