diff options
| author | Wolfgang Walther <walther@technowledgy.de> | 2025-07-12 15:06:19 +0200 |
|---|---|---|
| committer | Wolfgang Walther <walther@technowledgy.de> | 2025-07-12 15:06:19 +0200 |
| commit | acf5bc2417093a45a549caf7da0f3a5c9ef959aa (patch) | |
| tree | 4d62fd9e47c3e0dbdee32334e9c3282ba5b871eb /pkgs/development/python-modules/rangehttpserver | |
| parent | 9c492c323374a22963102ceb570dff269c01c2ae (diff) | |
workflows/labels: label rebuilds immediately
This fixes labeling in the context of the `pull_request` trigger. Of
course, this was supposed to immediately label rebuilds after eval
finishes, but we somehow lost this along the way. Rebuilds are still
labeled fairly soon, because the scheduled trigger will pick up the same
PR within 10 minutes again and then apply the rebuild labels. But of
course, immediate is better.
The reason this happened is, that we're looking at `item.pull_request`
only. This is the correct distinction between "issue items" and "pull
request items", which we both get back from the /issues endpoint. But
the payload for the `pull_request*` event doesn't contain this, so
labeling in this case was treated like an issue and skipped the whole
pull request part.
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions
