GitHub actions JSDoc update
plata opened this issue · 4 comments
We cannot push to master from GitHub actions. If we change the JSDoc in every PR, this will produce conflicts.
Maybe something like in https://github.com/cycjimmy/semantic-release-action#basic-usage
Alternatively we could think about pushing to a separate jsdoc branch. In addition this should only activate on pushes to the master branch. Ideally a new PR would be created as well.
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.
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 jsdoc branch instead it should try to update it. If it is needed we could also think about doing a force push to the jsdoc branch