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
Failed to publish a new draft of RFC6265bis. #1338
Comments
Erm. This is likely because I'm dumb and typed |
Oops. Those error messages are pretty obtuse, but hard to defend against. I guess that I could add to the existing pre-push hook for tags. Not that everyone engages those hooks. The default branch thing is down to GH being weird about its checkouts, for which an API token is needed just to get the branch name. That can be fixed in this repo by providing a token. |
So, I still think this was my fault, but when I uploaded another (correctly-spelled) tag, it failed in exactly the same way (presumably because it's publishing everything it hasn't already published?). I then deleted the incorrect I think we can close this as me being dumb. Perhaps @mnot, et al would like to follow up on the API token bits at some point in the future, though? |
Sure. @martinthomson what do we need to do? |
The only real change for this repo would be to suppress the default branch warnings, but that isn't really going to help with Mike's problem. I've opened martinthomson/i-d-template#253 to track the usability issue. |
https://github.com/httpwg/http-extensions/runs/1509108501?check_suite_focus=true shows the log of a failure to publish
draft-ietf-httpbis-rfc6265-07
. The relevant snipped from the failed step ("Upload to Datatracker") is below:As in #1031, I'll generate the text manually and upload it via datatracker, but I'd appreciate some help in case I did something wrong here, or someone looking into the workflow in case I didn't. :)
The text was updated successfully, but these errors were encountered: