-
Notifications
You must be signed in to change notification settings - Fork 142
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
feat: implement step to resolve conflict in release action PR #6670
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for ibm-products-web-components ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for carbon-for-ibm-products ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6670 +/- ##
==========================================
- Coverage 80.70% 80.68% -0.03%
==========================================
Files 397 397
Lines 12923 12923
Branches 4286 4286
==========================================
- Hits 10430 10427 -3
- Misses 2493 2496 +3
|
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.
Looks like it worked in your forked repo which is really cool! Just one small question, should there be a space between -X
and ours
?
It is |
Closes #6360
An additional step to resolve conflict by assuming the current
chore/<tag>-release
branch is ahead oforigin/main
. So, the-Xours
option specifies the--ours
strategy to merge by preferring current branch changes.What did you change?
How did you test and verify your work?
Manual (Github actions in forked repo)