There is a workflow to generate and update the sample project for referencing, which will be triggered on the merge commit to generate the sample project, commit and push all new changes.
Instead of generating & updating the sample project after merging new PRs into the develop, we can do it directly on each PR. That means, after making and pushing some changes in the template structure into a PR, there is a new workflow that will generate and push a new commit directly into that PR to show the new updates for the sample project.
Why
Original RFC #219
There is a workflow to generate and update the
sample
project for referencing, which will be triggered on the merge commit to generate thesample
project, commit and push all new changes. Instead of generating & updating the sample project after merging new PRs into thedevelop
, we can do it directly on each PR. That means, after making and pushing some changes in the template structure into a PR, there is a new workflow that will generate and push a new commit directly into that PR to show the new updates for the sample project.To achieve this:
generate_mason_bundle
Who Benefits?
Developers