-
Notifications
You must be signed in to change notification settings - Fork 28
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
perf: added workflow to comment next version on PR raise trigger #143
perf: added workflow to comment next version on PR raise trigger #143
Conversation
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.
Why not just use semantic release with a different config instead of adding new logic ourselves.
See the examples in the replies in this issue: semantic-release/semantic-release#1647
@feanil I tried above mentioned suggestions and solutions. It came out to be the same outcome as before. Please let me know if we can go further with the solution provided by this PR or we should explore other github actions for expected version of release. |
@huniafatima-arbi I think you'll want to run with --no-ci so that it skips the environment verifications and just spits out the version number. |
Description
Semantic release was being used to comment the release version upon merging the PR. We needed to know the expected version of the release prior to merging. This PR adds the workflow to comment the expected release version.
Ticket Link
openedx/wg-frontend#139
Test
Tested the workflow on following PR
edx/frontend-component-header-edx#586