No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind
Chore
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
4 participants
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo/act!168
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch ":nif-fix-make-node-tool-non-volatile-6de25a53bcba30bda7014e3172a241e4e531d807"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
https://github.com/nektos/act/pull/2372
fix: make node tool non volatile
Currently downgrading node via setup-node can break later actions
fix it and lookup on startup
fix problems
cascading-pr updated at forgejo/runner#654
46d0e2eea3bb075ab2b9cascading-pr updated at forgejo/runner#654
Closing this until the discussion on how to approach catching up with ACT concludes. It can be re-opened when a strategy was decided but in the meantime please @achyrva refrain from opening new ones.
test
@ -571,4 +570,1 @@var containerArgs []stringif action.Runs.Using == model.ActionRunsUsingSh {why this if condition was dropped? doesn't it break something 🤔
Good catch, it is not part of the original commit. I reviewed the original commit because there was no indication of conflict in !168 (commit
c1a1722cbe)And I missed they are actually different.
I'll revert that now.
dd138c24f8