Compare commits

..

3 commits

Author SHA1 Message Date
4736202e36
Merge 0190e46c72 into 2567f0ae8b 2024-08-25 15:17:55 +00:00
releaser-pleaser
0190e46c72 chore(main): release v0.2.0 2024-08-25 15:17:52 +00:00
2567f0ae8b
ci: run on pr updates from main branch (#30)
With `pull_request`, we run in the context of the pull request branch.

- This means we run with the code from the PR branch, possibly breaking
  the current release PR for this repo with in-progress, unreviewed changes.
- This means that the secret is not available on Pull Requests from
  forks.

Switching to `pull_request_target` means we always run in the scope of
the original repository. The secret is available and the code is checked
out from our main branch.

`pull_request_target` has security considerations, but they do not apply
here as we do not check out or run code from the (external, malicious) PR.
2024-08-25 17:16:43 +02:00

View file

@ -3,8 +3,8 @@ name: releaser-pleaser
on: on:
push: push:
branches: [main] branches: [main]
# TODO: use pull_request_target to avoid tainting the actual release PR with code from open feature pull requests # Using pull_request_target to avoid tainting the actual release PR with code from open feature pull requests
pull_request: pull_request_target:
types: types:
- edited - edited
- labeled - labeled
@ -14,10 +14,13 @@ permissions: {}
jobs: jobs:
releaser-pleaser: releaser-pleaser:
# TODO: if: push or pull_request.closed
runs-on: ubuntu-latest runs-on: ubuntu-latest
steps: steps:
- name: Checkout - name: Checkout
uses: actions/checkout@v4 uses: actions/checkout@v4
with:
ref: main
- name: Set up Go - name: Set up Go
uses: actions/setup-go@v5 uses: actions/setup-go@v5