mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #4] Clean install on macOS via Brew leads to a panic #3
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Originally created by @fbartho on GitHub (Jan 15, 2019).
Original GitHub issue: https://github.com/nektos/act/issues/4
@cplee commented on GitHub (Jan 15, 2019):
@fbartho can you share your
main.workflow?@fbartho commented on GitHub (Jan 15, 2019):
@cplee https://gist.github.com/fbartho/5bccef3a0a8f31ba47d2523424b547c8 -- I don't know that this is sensitive, but it would feel more reassuring to delete it once you have a copy, so please comment back when you've downloaded it.
@cplee commented on GitHub (Jan 15, 2019):
@fbartho got it...and i'm able to reproduce it. I see the problem...thanks for reporting!
@fbartho commented on GitHub (Jan 15, 2019):
@cplee glad to help! Do please let me know what the ultimate fix was. I'm guessing some sort of parse error due to my comment blocks or something. Haha
@cplee commented on GitHub (Jan 16, 2019):
@fbartho i haven't released a new version yet, but the code on
mastershould address this. i can't confirm as i don't have your./scripts/github_actions. want to try it out and confirm before i cut another release?@cplee commented on GitHub (Jan 16, 2019):
@fbartho i've included a fix for this in
v0.0.4. feel free to reopen if this issue persists!@fbartho commented on GitHub (Jan 16, 2019):
Sorry I didn't get a chance to test master! I've verified that v0.0.4 resolves my concerns!