| 20 Mar 2024 |
 infinisil | We can just give the github action permission for that | 23:26:01 |
| infinisil | The separate machine account workaround is only needed to trigger workflows from PRs triggered by workflows | 23:26:30 |
 Philip Taron (UTC-8) | In reply to @infinisil:matrix.org
Would be nicer if it would automatically do a weekly PR, which when merged creates a release
The separate machine account workaround is only needed to trigger workflows from PRs triggered by workflows
I'm getting confused.
We do want an automatic-ish update of dependencies. ✅ -- but with an explicit human in the loop hitting the merge button.
We do want an automatic-ish release process. ✅ -- but with an explicit human in the loop to move from draft to public.
So, we want a separate machine account, so that the CI all fits together, and doesn't get wedged like #14 did.
Right?
| 23:34:24 |
| infinisil | Ahh right! | 23:34:53 |
| infinisil | I'm getting confused too 😅 | 23:34:59 |
| infinisil | Philip Taron (UTC-8): Concretely, how about this:
- The version gets bumped (probably in
Cargo.toml) with a PR
- This can either happen manually if somebody remembers
- Otherwise a bot will automatically do that with a PR that just does the version bump
- A separate workflow, triggered on main branch pushes, takes care to do the release whenever the version gets bumped
| 23:39:22 |
| infinisil | * Philip Taron (UTC-8): Concretely, how about this:
-
The version gets bumped (probably in Cargo.toml) with a PR
- This can either happen manually if somebody remembers
- Otherwise a bot will automatically do that with a PR that just does the version bump
-
A separate workflow, triggered on main branch pushes, takes care to do the release whenever the version gets bumped
| 23:39:39 |
| infinisil | For 1. we need the separate machine account, but it doesn't need any permissions because it just creates a PR. For 2. we don't need a separate machine account and can just give the workflow the permission to push a tag/release | 23:40:37 |
