ci: add automerge dependencies to the next release milestone#240
Conversation
zimeg
added
code health
| github-token: "${{ secrets.GITHUB_TOKEN }}" | ||
| - name: Milestone | ||
| if: steps.metadata.outputs.update-type == 'version-update:semver-patch' || steps.metadata.outputs.update-type == 'version-update:semver-minor' | ||
| run: gh pr edit --milestone "Next Release" "$PR_URL" |
There was a problem hiding this comment.
praise: Oooh, it's nice that we can use the GH CLI to specify the Milestone name!
There was a problem hiding this comment.
@mwbrooks I thought the exact same! It's nice that we use a consistent name for the next release and I'm wondering if we can mirror this elsewhere for later changes...
There was a problem hiding this comment.
Good point, if this works well, then we can revisit the Bolt / SDK milestone organization to keep it consistent everywhere and make automation easier.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #240 +/- ##
==========================================
- Coverage 63.00% 62.98% -0.03%
==========================================
Files 212 212
Lines 21857 21857
==========================================
- Hits 13772 13766 -6
- Misses 7020 7024 +4
- Partials 1065 1067 +2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
2 participants
Summary
This PR follows up on #239 to also add automerge dependencies to the "Next Release" milestone for release notes 📚 ✨
Requirements