You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if [[ "${{ steps.getPRInfo.outputs.REPO_FULL_NAME }}" != ${{ github.repository }} ]] && [[ "${{ steps.getPRInfo.outputs.REPO_FULL_NAME }}" != "Expensify/Mobile-Expensify" ]]; then
38
+
if [[ "${{ steps.getPRInfo.outputs.REPO_FULL_NAME }}" != ${{ github.repository }} ]] && [[ ! "${{ steps.getPRInfo.outputs.REPO_FULL_NAME }}" =~ Expensify/Mobile-Expensify* ]]; then
28
39
echo "::error::❌ Cherry picks are only supported for the Expensify/App and Expensify/Mobile-Expensify repositories. Found: ${{ steps.getPRInfo.outputs.REPO_FULL_NAME }}"
This PR had conflicts when we tried to cherry-pick it to staging. You'll need to manually perform the cherry-pick, using the following steps:
186
+
This PR had conflicts when we tried to cherry-pick it to ${{ inputs.TARGET }}. You'll need to manually perform the cherry-pick, using the following steps:
187
187
188
188
\`\`\`bash
189
189
git fetch
@@ -194,25 +194,25 @@ jobs:
194
194
Then manually resolve conflicts, and commit the change with \`git cherry-pick --continue\`. Lastly, please run:
git commit --amend -m "\$(git log -1 --pretty=%B)" -m "(cherry-picked to ${{ inputs.TARGET }} by ${{ github.actor }})"
198
198
\`\`\`
199
199
200
-
That will help us keep track of who triggered this CP. Once all that's done, push your changes with \`git push origin ${{ steps.getBranchName.outputs.CONFLICT_BRANCH_NAME }}\`, and then open this PR for review.
200
+
This last part is important. It will help us keep track of who triggered this CP, and will ensure that version bumps are tracked correctly. Once all that's done, push your changes with \`git push origin ${{ steps.getBranchName.outputs.CONFLICT_BRANCH_NAME }}\`, and then open this PR for review.
201
201
202
202
Note that you **must** test this PR, and both the author and reviewer checklist should be completed, just as if you were merging the PR to main.
203
203
204
-
_Pro-tip:_ If this PR appears to have conflicts against the _staging_ base, it means that the version on staging has been updated. The easiest thing to do if you see this is to close the PR and re-run the CP.
204
+
_Pro-tip:_ If this PR appears to have conflicts against the _${{ inputs.TARGET }}_ base, it means that the version on ${{ inputs.TARGET }} has been updated. The easiest thing to do if you see this is to close the PR and re-run the CP.
Copy file name to clipboardExpand all lines: .github/workflows/createNewVersion.yml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -131,7 +131,7 @@ jobs:
131
131
git commit -m "Update version to ${{ steps.bumpVersion.outputs.NEW_VERSION }}"
132
132
if ! git push origin main; then
133
133
echo "Race condition! Mobile-Expensify main was updated while this workflow was running, so push failed. Fetching remote, rebasing, and retrying push once."
134
-
git fetch origin main --depth=1
134
+
git fetch origin main
135
135
if ! git rebase origin/main; then
136
136
echo "::error:: Rebase failed while retrying Mobile-Expensify push"
137
137
exit 1
@@ -159,7 +159,7 @@ jobs:
159
159
git commit -m "Update Mobile-Expensify submodule version to ${{ steps.bumpVersion.outputs.NEW_VERSION }}"
160
160
if ! git push origin main; then
161
161
echo "Race condition! E/App main was updated while this workflow was running, so push failed. Fetching remote, rebasing, and retrying push once."
162
-
git fetch origin main --depth=1
162
+
git fetch origin main
163
163
if ! git rebase origin/main; then
164
164
echo "::error:: Rebase failed while retrying Mobile-Expensify push"
0 commit comments