Skip to content

Commit

Permalink
Clarify the trigger context dimension values (#2961)
Browse files Browse the repository at this point in the history
Provide a bit more precise definitions of the `commit` and `build`
trigger values, especially to make it clear that `build` could be
used for the event of promoting draft builds as well.
  • Loading branch information
psss authored and happz committed Jun 2, 2024
1 parent 95c954a commit 7eaf241
Showing 1 changed file with 7 additions and 3 deletions.
10 changes: 7 additions & 3 deletions spec/context/trigger.fmf
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,13 @@ description: |

commit
Project source code has changed. This can be either a
pull/merge request or a new commit pushed to a branch.
pull/merge request creation or update, new branch created
or a new commit pushed to an existing branch.

build
There has been a new package built in koji or brew and is
available for testing.
There has been a new official package built in koji or
brew. It can be a non-scratch build created directly or a
`draft build`__ which has been promoted to non-draft.

update
A new bodhi update or errata advisory with one or more
Expand All @@ -27,6 +29,8 @@ description: |
This context dimension will usually be provided from the
command line.

__ https://docs.pagure.org/koji/draft_builds/

example: |
summary: Full test coverage (takes three days)
discover:
Expand Down

0 comments on commit 7eaf241

Please sign in to comment.