Eric Ernst 24796d2f25 kata-deploy: for testing, make sure we use the PR branch ...

Since we are already checking that only an admin is triggering the job,
let's go ahead and make sure we are testing against the PR itself. This
will ensure that we are exercising changes to kata-deploy tooling, which
is important for this test.

While at it, cleanup and simplify some of the tarball creation.

Fixes: #3586

Signed-off-by: Eric Ernst <eric_ernst@apple.com>

2022-02-01 10:53:30 -08: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

workflows: Ensure a label change re-triggers the actions

2022-01-18 14:39:01 +01:00

kata-deploy-push.yaml

workflows: Fix typo in kata-deploy-push action

2022-01-19 11:05:58 +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

workflows: Ensure a label change re-triggers the actions

2022-01-18 14:39:01 +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

workflows: Ensure a label change re-triggers the actions

2022-01-18 14:39:01 +01:00

static-checks.yaml

versions: bump golang to 1.17.x

2021-11-11 10:43:18 +01:00