Fabiano Fidêncio 88a70d32ba Revert "workflows: Ensure a label change re-triggers the actions" ...

This reverts commit 7a879164bd, as it's
been proved that re-triggering the checks at every single change is more
painful than having to close / re-open a PR in case we ever use the
`force-skip-ci` label again.

Fixes: #2804

Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com>

2022-02-04 00:01:21 +01:00

..

add-issues-to-project.yaml

action: Add issue to project and move to "In progress" on linked PR

2020-09-14 09:24:54 +01:00

commit-message-check.yaml

Revert "workflows: Ensure a label change re-triggers the actions"

2022-02-04 00:01:21 +01:00

kata-deploy-push.yaml

Revert "workflows: Ensure a label change re-triggers the actions"

2022-02-04 00:01:21 +01:00

kata-deploy-test.yaml

kata-deploy: for testing, make sure we use the PR branch

2022-02-01 10:53:30 -08:00

move-issues-to-in-progress.yaml

Revert "workflows: Ensure a label change re-triggers the actions"

2022-02-04 00:01:21 +01:00

PR-wip-checks.yaml

workflows: Ensure force-skip-ci skips all actions

2022-01-18 14:37:32 +01:00

release.yaml

release: Use ${GOPATH}/bin/yq for upload-libseccomp-tarball action

2021-11-11 13:42:12 +09:00

require-pr-porting-labels.yaml

workflows: Ensure force-skip-ci skips all actions

2022-01-18 14:37:32 +01:00

snap-release.yaml

ci: snap: Fetch history to all branches and tags

2021-06-16 13:34:09 -04:00

snap.yaml

Revert "workflows: Ensure a label change re-triggers the actions"

2022-02-04 00:01:21 +01:00

static-checks.yaml

Revert "workflows: Ensure a label change re-triggers the actions"

2022-02-04 00:01:21 +01:00