-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release workflow for monorepo #139
Conversation
Codecov Report
@@ Coverage Diff @@
## main #139 +/- ##
==========================================
+ Coverage 57.12% 58.40% +1.28%
==========================================
Files 269 372 +103
Lines 6316 8677 +2361
Branches 1434 1962 +528
==========================================
+ Hits 3608 5068 +1460
- Misses 2566 3384 +818
- Partials 142 225 +83
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Here's a test run, how it would now generate PR's: hobbies1.1.0 (2023-01-10)Features
Bug Fixes
events0.4.0 (2023-01-10)Features
Bug Fixes
sports0.4.0 (2023-01-10)Features
Bug Fixes
components0.1.0 (2023-01-10)Features
Bug Fixes
common-i18n0.1.0 (2023-01-10)Features
Bug Fixes
federation-router1.1.0 (2023-01-10)Features |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As described in the earlier meetings.
Description
Setup Release Please Github workflow for automating changelogs,
versioning and releases for the apps and components in this repo.
In order for this to work, all commits need to be in conventional commits style.
After a PR with changes is merged to master, the workflow will detect changes and create a "Release PR" with the changes related to the app/component. These Release PR's will accumulate changes and update their versions until they're merged. After merging, the Release PR will create a version tag, which should trigger a release action just like creating a tag manually and pushing would. Tags are prefixed with the component name, as defined in the package.json.
This is just the basic setup and might need some tweaking still.
Issues
Closes
HH-280:
Related
Testing
Automated tests
Manual testing
Screenshots
Additional notes