-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
act shouldn't complain when there's no remote repo #2493
Comments
The main issue is |
This bypasses the remote warning introduced in #2169 |
Is there any update to this? My script still works but this warning bothers me because it is cluttering the stdout logs. In that PR 2169, the merging is blocked. @stephenwithav |
None that I'm aware of. @ChristopherHX? |
None from my side as well, except permissions. Does not look differently for my account. @stephenwithav I'm not that far away from hard forking to actions-oss, I cannot do anything without cplee / inactive maintainers. two approval rule is required to let mergify do the merge, that I'm not permitted to perform myself. My primary focus left act this year, some PR's changed to closed from my side and no new changes from this month. |
I'll be an active contributor if you fork, @ChristopherHX. If I had considered rewriting it from the ground up, but faced the same hard fork concerns. Refactoring a fork may be a better option. |
Act version
5a1e0d9, built with my PR
Feature description
act
complains when there's no remote repo.Sometimes, a dev just wants to test ideas locally before creating a remote repo. :)
act/pkg/model/github_context.go
Line 172 in ccd28e7
The text was updated successfully, but these errors were encountered: