workflows: Ensure a label change re-triggers the actions

This is needed in order to ensure that, for instance, if `force-skip-ci`
label is either added or removed later, the jobs related to the actions
will be restarted and accordingly checked.

Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>
This commit is contained in:
Fabiano Fidêncio 2022-01-18 14:39:01 +01:00
parent d87ab14fa7
commit 7a879164bd
4 changed files with 24 additions and 2 deletions

View File

@ -5,6 +5,8 @@ on:
- opened
- reopened
- synchronize
- labeled
- unlabeled
env:
error_msg: |+

View File

@ -1,6 +1,15 @@
name: kata deploy build
on: [push, pull_request]
on:
pull_request:
types:
- opened
- edited
- reopened
- synchronize
- labeled
- unlabeled
push
jobs:
build-asset:

View File

@ -10,6 +10,8 @@ on:
types:
- opened
- reopened
- labeled
- unlabeled
jobs:
move-linked-issues-to-in-progress:

View File

@ -1,5 +1,14 @@
name: snap CI
on: ["pull_request"]
on:
pull_request:
types:
- opened
- synchronize
- reopened
- edited
- labeled
- unlabeled
jobs:
test:
runs-on: ubuntu-20.04