To verify the generated project by the template, we should have a workflow to generate the sample project and commit changes to the repository on each PR. That means, after making and pushing some changes in the template structure into a PR, the new workflow that will generate and push a new commit directly into that PR to show the new updates for the sample project.
This approach has some concerns are:
Pushing a new commit via a bot account after a commit from the author will cause the author can not push new commits without pulling or force-pushing π Since, the bot pushes the new commits to update the project, the author can ignore those and force-push new update commits into their PRs. The bot will push new commits afterward by combining all the changes in the final sample project β
The bot will not push an update commit without changes β
We can review both all changes from the template structure and the generated project result (sample) at the same time in one PR β
[!NOTE]
We must build a simple initial script to generate the template to push the changes.
Why
To verify the generated project by the template, we should have a workflow to generate the
sample
project and commit changes to the repository on each PR. That means, after making and pushing some changes in the template structure into a PR, the new workflow that will generate and push a new commit directly into that PR to show the new updates for the sample project.This approach has some concerns are:
the author can ignore those and force-push new update commits into their PRs
. The bot will push new commits afterward by combining all the changes in the final sample project βnot push an update commit without changes
βthe template structure
andthe generated project result
(sample) at the same time in one PR βWho Benefits?
Developers