Added workflow to generate releases #142
Conversation
| uses: softprops/[email protected] | ||
| with: | ||
| files: Wall-E.zip | ||
| tag_name: ${{ env.TIMESTAMP }} |
There was a problem hiding this comment.
Are you sure that we want to use the timestamp for the release?
There was a problem hiding this comment.
The timestamp variable creates a tag with the year of trigger of the action. Check above for it’s logic.
| files: Wall-E.zip | ||
| tag_name: ${{ env.TIMESTAMP }} | ||
| name: Wall-E Release ${{ env.TIMESTAMP }} | ||
| body: This automated release contains the latest Wall-E source code with the submodules. It was triggered by following commit - ${{ github.event.head_commit.id }} |
There was a problem hiding this comment.
So, this will be triggered after each commit?
There was a problem hiding this comment.
We don't want it to be released after each commit as possibility of reverting is significant, maybe there should be some trigger word added in the commit to trigger the release
There was a problem hiding this comment.
We can instead shift to first getting all development commits on the dev branch and keep the main branch only for releases. I can make the changes in the contribution guide for redirecting contributors to merge in the main branch.
There was a problem hiding this comment.
Or, we can have a separate release branch.
There was a problem hiding this comment.
Aah, I think having dev branch is better and then just merge all changes to main
An example release. |
SuperChamp234
force-pushed
the
master
branch
4 times, most recently
from
cb8fa19 to
0803303
Compare
SuperChamp234
force-pushed
the
master
branch
from
0803303 to
803db2d
Compare
This PR includes the addition of a github action that will make a github release containing the source code with the Wall-E folder as a zip file, including all submodules.
This PR aims to help cloning the repository during workshops, as an alternative to
git clonePlease review.