-
Notifications
You must be signed in to change notification settings - Fork 49
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
GitHub actions JSDoc update #1233
Comments
Maybe something like in https://github.com/cycjimmy/semantic-release-action#basic-usage |
Alternatively we could think about pushing to a separate |
Yes, but this also has some drawbacks. E.g. what happens if the jsdoc branch is not merged before the action wants to create it again? In general, I would like to avoid manual interaction. |
In this case it should not recreate the |
As explained in #1233, this should not be the final solution. However, it will work for the meantime while not too many PRs must be handled in parallel.
We cannot push to master from GitHub actions. If we change the JSDoc in every PR, this will produce conflicts.
The text was updated successfully, but these errors were encountered: