-
Notifications
You must be signed in to change notification settings - Fork 1
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
Improve onboarding for storing badges on an orphan branch #4
Comments
This used to be possible via the API but it doesn't work anymore. Here's a chopped down summary of my (long) chat with GitHub support that took place over ~ a month: @chris48s wrote:
GitHub support wrote:
@chris48s wrote:
GitHub support wrote::
so.. long and short of this is trying to do this via the API is now a dead-end. I think the options now are:
|
For now I've settled on the following solution:
This is still not quite as elegant as I would ideally like. |
Maybe it is still worth looking at doing this in JS. Not intrinsically connected to whether it is done using JS in core or using bash in a standalone action, but either way one thing I'm slightly worried about is leaving the working tree in an unexpected state. Currently create-orphan-branch handles this using:
Maybe |
Is there anything I can learn from https://github.com/s0/git-publish-subdir-action/blob/develop/action/src/index.ts ? |
This is probably the ideal solution for where to store the badges. Currently this is just handled as a documentation point
https://github.com/action-badges/core/blob/main/docs/github-action.md#storing-your-badges
I tried this naive approach:
but it isn't concurrency-safe: If there are multiple workflows generating badges some of them will probably fail on the first run.
How can I do this in a concurrency-safe way?
The text was updated successfully, but these errors were encountered: