-
Notifications
You must be signed in to change notification settings - Fork 46
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
🍒 Merge changes from PR #244 to release-v1.6.0 #248
Conversation
@Siyasanga The auto cherry picking for the changes failed here. What you need to do is follow the instructions mentioned in the PR description to manually cherry-pick the commits and then resolve the conflicts |
@Zangetsu101 I'm struggling to run these command, could it be because I deleted the bug branch after I merged into To try and rectify this, I restored the branch by pushing my local(
Is failing, I'm not sure whether I was supposed to replace From my understanding, which I'm not very confident about, is that we have a new branch( |
Yes that is correct |
* Also update the precedingFieldId of the defaultAddressConfiguration (#7404)[opencrvs/opencrvs-core#7404]
* Also update the precedingFieldId of the defaultAddressConfiguration (#7404)[opencrvs/opencrvs-core#7404]
* Also update the precedingFieldId of the defaultAddressConfiguration (#7404)[opencrvs/opencrvs-core#7404]
* Also update the precedingFieldId of the defaultAddressConfiguration (#7404)[opencrvs/opencrvs-core#7404]
We missed adding an entry into the CHANGELOG.md to document the changes we made and why we had to make changes opencrvs/opencrvs-core#7404
6c03457
to
89abe56
Compare
Thanks @Zangetsu101 I've cherry-picked the commits to this branch, but I don't have merge permissions Can you please merge if you are also happy with the changes |
Automated PR to merge changes from develop to release-v1.6.0
I failed to cherry-pick the changes automatically because of the following:
To continue manually you can use these commands: