The release workflow used to release the 0.3.0 version performs too much pushes (3). See https://github.com/process-analytics/bpmn-visualization-R/blob/v0.3.0/.github/workflows/release.yml
This triggers extra builds and documentation publishing.
We should do the commits in sequence like we do today. But perform a single push (commits and tags) at the end.
That way, we will reduce GitHub Actions usage and if an issue occur during a commit, nothing will have been pushed allowing to rerun the workflow.
Note: do not forget to update the definition of the workflow in the playground repository (it serves as a test here)
The release workflow used to release the 0.3.0 version performs too much pushes (3). See https://github.com/process-analytics/bpmn-visualization-R/blob/v0.3.0/.github/workflows/release.yml
This triggers extra builds and documentation publishing.
We should do the commits in sequence like we do today. But perform a single push (commits and tags) at the end.
That way, we will reduce GitHub Actions usage and if an issue occur during a commit, nothing will have been pushed allowing to rerun the workflow.
Note: do not forget to update the definition of the workflow in the playground repository (it serves as a test here)