|
|
ccdecda26c
|
Ensure we check out current commit
Before we were checking out the 'github.ref', which described the
"fully-formed ref of the branch or tag that triggered the workflow"
instead of the actual commit we want.[1] If there are commits above the
commit that triggered the current run (e.g. we pushed multiple to main
or similar), we would compare the wrong (head) commit.
Removing the 'ref:' option should check out the correct SHA instead.[2]
If it turns out it does not, we could still manually supply
'${{ github.sha }}'.
[1]: https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs#github-context
[2]: https://github.com/actions/checkout
|
2025-03-08 17:44:05 +01:00 |
|
|
|
c178fb1f44
|
Allow concurrent build jobs but not deploys
|
2025-03-08 17:44:04 +01:00 |
|
|
|
6a1bb4ea1e
|
Fix repo deployment workflow
|
2025-03-08 16:24:45 +01:00 |
|
|
|
cf6641bfff
|
Don't automatically remove obsolete packages from repo
|
2025-03-06 20:23:47 +01:00 |
|
|
|
bc5d40f68a
|
Create separate deploy job
|
2025-03-06 09:56:11 +01:00 |
|
|
|
642c363d8d
|
Check diff to parent commit for non-merge commits
|
2025-03-06 08:27:42 +01:00 |
|
|
|
bb6ed04bf5
|
Check out current ref
|
2025-03-06 08:27:42 +01:00 |
|
|
|
c64a1f6c81
|
Add repo index page
|
2025-03-06 08:27:41 +01:00 |
|
|
|
94521d0b1b
|
Add build workflow
|
2025-03-06 08:27:38 +01:00 |
|
|
|
4a1ae17834
|
Add void-packages change detection script
|
2025-03-05 21:16:29 +01:00 |
|
