CI: restrict deployment only to push events on `master`

realaravinth commented

2022-04-17 13:34:29 +00:00

Owner

Currently deployment steps are also run on PRs, which are failing because Woodpecker secrets are configured to be available only on pushes.

Currently deployment steps are also run on [PRs](https://gitea.hostea.org/Hostea/website/pulls/2), which are failing because Woodpecker secrets are configured to be available only on pushes.

👍 1

realaravinth self-assigned this 2022-04-17 13:34:29 +00:00

dachary commented

2022-04-17 14:06:17 +00:00

Owner

Is it enough to just untick this checkbox?

Is it enough to just untick [this checkbox](https://woodpecker.hostea.org/Hostea/website/settings)? ![image](/attachments/46296bb2-5486-48aa-b397-7069f7053f04)

image.png

55 KiB

realaravinth commented

2022-04-17 15:34:58 +00:00

Poster

Owner

That would disable CI entirely on pull requests, which means we won't be able to check if the changes proposed build successfully. Only the deployment step needs to be disabled for pull requests, I believe there are provisions to do that with Woodpecker.

dachary commented

2022-04-17 15:51:34 +00:00

Owner

Ah, dang, sorry I misunderstood the problem.

👍 1

dachary added the

Bug

label 2022-05-10 08:21:52 +00:00

CI: restrict deployment only to push events on master #3

CI: restrict deployment only to push events on `master` #3