Skip to content

Conversation

@ocrvs-bot
Copy link
Contributor

Automated PR to merge changes from develop to release-v1.X.Y

I failed to cherry-pick the changes automatically because of the following:

[auto-pr-release-v1.X.Y-753-13563 4dc53d3d] Mk placeOfBirth field shows only acfive facilities
Author: Siyasanga <[email protected]>
Date: Wed May 21 10:33:21 2025 +0200
1 file changed, 1 insertion(+), 1 deletion(-)
Auto-merging src/form/death/required-fields.ts
[auto-pr-release-v1.X.Y-753-13563 551bf0bf] Ensure the placeOfDeath only show active facilities
Author: Siyasanga <[email protected]>
Date: Mon May 26 09:28:11 2025 +0200
1 file changed, 1 insertion(+), 1 deletion(-)
Auto-merging CHANGELOG.md
CONFLICT (content): Merge conflict in CHANGELOG.md
error: could not apply bc4897f8... Record PR changes to the CHANGELOG

To continue manually you can use these commands:

git fetch origin auto-pr-release-v1.X.Y-753-13563:auto-pr-release-v1.X.Y-753-13563
git fetch origin ocrvs-9311:ocrvs-9311

git checkout auto-pr-release-v1.X.Y-753-13563
git reset --hard HEAD~1  # Remove placeholder commit
git cherry-pick 909762a7be544eb12489a8e54530fe5dee98b598~..bc4897f824c9c84f5a1d2897c75df5baccddb8bd

Individual commits:

bc4897f8 Record PR changes to the CHANGELOG
c392134b Ensure the placeOfDeath only show active facilities
909762a7 Mk placeOfBirth field shows only acfive facilities

@github-actions

This comment has been minimized.

@Siyasanga Siyasanga force-pushed the auto-pr-release-v1.X.Y-753-13563 branch from f37d6bd to c6febdc Compare June 4, 2025 18:23
@github-actions
Copy link
Contributor

This PR has been marked with label stale Since it has been inactive for 20 days. It will automatically be closed in 10 days if no further activity occurs.

@github-actions github-actions bot added the Stale PR is inactive for many days label Jun 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Stale PR is inactive for many days

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants