-
Notifications
You must be signed in to change notification settings - Fork 8
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
audit-check default branch renamed from master
to main
#26
Comments
That sounds like the date when I published v2.0.0 (#25). I didn't personally rename or delete any branches however, just tagged a The development branch is indeed now named I'm not sure what to do as a resolution here besides tell you to rename the branch in your config. We can mirror |
master
to main
I think that rename is what broke tokio's security audit workflow. Personally I would weigh breaking 2 weeks of new users of audit-check against breaking years of existing users and find that changing the branch name back would be better than leaving as main. Though to be honest maybe this is just what we all get for using a branch rather than a tag like we should. I've renamed this issue to be about the rename since I think it's clear to me now that that's what caused the breakage. |
I'm not sure how that happened. I don't remember doing it. I don't remember seeing any of the dialogs that the branch had been renamed. Perhaps npm did it? I don't know. I renamed it back (which took a bit of doing, as I had to search around the UI for where to even do it, which again makes me wonder how it was renamed in the first place) |
we've been using |
Ugh, I guess I can have the two mirror each other |
I've been getting GitHub Actions errors on my fork of tokio to do with audit-check
Looks like tokio's been getting it too
I don't see this action on the Marketplace when I search for audit-check. Has it somehow been removed? I noticed the default branch for this repo is called
main
, notmaster
. Was that changed around the 24th of September? That's when I started seeing the error.The text was updated successfully, but these errors were encountered: