[#525] 1/2 - Create a new workflow to automate the release pull request creation #557
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
luongvo
temporarily deployed
to
template-compose
GitHub Actions
Inactive
luongvo
force-pushed
the
feature/525-create-release-pr-workflow
branch
from
758a2fe to
78d43e4
Compare
Kover report for template-compose:🧛 Template - Compose Unit Tests Code Coverage:
|
| File | Coverage |
|---|
Modified Files Not Found In Coverage Report:
changelog-release.json
create_release_pr.yml
Codebase cunningly covered by count Shroud 🧛
Generated by 🚫 Danger
luongvo
force-pushed
the
feature/525-create-release-pr-workflow
branch
from
78d43e4 to
1e16f8e
Compare
luongvo
force-pushed
the
feature/525-create-release-pr-workflow
branch
2 times, most recently
from
72acad8 to
c2c8dc9
Compare
luongvo
had a problem deploying
to
template-compose
GitHub Actions
Error
luongvo
force-pushed
the
feature/525-create-release-pr-workflow
branch
from
c2c8dc9 to
031475a
Compare
luongvo
temporarily deployed
to
template-compose
GitHub Actions
Inactive
luongvo
changed the title
luongvo
temporarily deployed
to
template-compose
GitHub Actions
Inactive
luongvo
requested review from
AVI5HEK,
chornerman,
doannimble,
hoangnguyen92dn,
kaungkhantsoe,
lydiasama,
manh-t,
minhnimble,
ryan-conway,
sleepylee,
thiennguyen0196,
toby-thanathip and
Wadeewee
as code owners
luongvo
force-pushed
the
feature/525-create-release-pr-workflow
branch
from
031475a to
3fb0c4a
Compare
luongvo
temporarily deployed
to
template-compose
GitHub Actions
Inactive
luongvo
force-pushed
the
feature/525-create-release-pr-workflow
branch
from
3fb0c4a to
cdbde1a
Compare
luongvo
temporarily deployed
to
template-compose
GitHub Actions
Inactive
chornerman
reviewed
Jan 8, 2024
| contents: write | ||
| pull-requests: write | ||
| steps: | ||
| - name: Checkout the latest code |
There was a problem hiding this comment.
Suggested change
| - name: Checkout the latest code | |
| - name: Check out the latest code |
| pull-requests: write | ||
| steps: | ||
| - name: Checkout the latest code | ||
| uses: actions/checkout@v3 |
There was a problem hiding this comment.
I think we can use actions/checkout@v4 🙏🏼
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#525
What happened 👀
Create a new workflow
create_release_pr.ymlto automate the Release pull request creation:tagon the main branch to the latest HEAD on thedevelop.Insight 📝
To generate the release change log like our Release PR, use https://github.com/mikepenz/release-changelog-builder-action. It helps us generate the change log from a config file, like what we did with https://github.com/release-drafter/release-drafter from [#100] Add new workflow to generate release note and version tag automatically #245. However, https://github.com/mikepenz/release-changelog-builder-action does not require adding its app to our GitHub organization and can be reused to generate the change log texts for App Distribution release notes or even create releases like release-drafter.
To create the pull request by checking out a new release branch from develop, we can NOT use https://github.com/peter-evans/create-pull-request because it requires stage changes to create PR. Instead, I realized we can create PR using GitHub CLI 🤩
Before creating the release PR, we must check out a new release branch from the current
develop.To fetch corresponding
milestoneinfo (assuming the milestone matches the current version name), while GitHub CLI does not support milestone API officially, we can use an extension called https://github.com/valeriobelli/gh-milestone 🤩This command helps us to get the milestone URL from the milestone name = current version:
Proof Of Work 📹
A sample generated Release PR for the current
develop👉main#560 🎉Run log: https://github.com/nimblehq/android-templates/actions/runs/6971579676/job/18971937503