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
You'll observe that the app version on the deploy checklist increases. (BUG)
There should be a merge conflict with the CP PR.
Close the CP PR without resolving conflicts or merging it.
Then without running any other CP's first, close the checklist to run a production deploy.
Expected Result:
The production and staging deploys should complete successfully, and we should have a new checklist.
Actual Result:
The production and staging deploys complete successfully, but creating a new checklist fails with the following type of error:
Found tag of previous StagingDeployCash: 1.1.22-1
Getting pull requests merged between the following refs: 1.1.22-1 1.1.22-2
Running command: git log --format="{[%B]}" 1.1.22-1...1.1.22-2
fatal: ambiguous argument '1.1.22-1...1.1.22-2': unknown revision or path not in the working tree.
Where in this case 1.1.22-1 is the tag that was posted in the deploy checklist, but never actually created.
Workaround:
DANGER:
Manually update the checklist to have the tag matching the latest production deploy (GitHub Release).
Re-run the finishReleaseCycle.yml workflow
IMPORTANT NOTE: This will attempt to deploy all the code from staging to production. It's imperative that you manually kill the workflow before that happens. It's best to kill the updateProtectedBranch workflow that's attempting to merge the code from staging -> production, but if you're too slow then you can kill the deploy.yml or platformDeploy.yml as well.
We've seen similar problem that suggests a similar solution to this, namely: "Only update the app version on the StagingDeployCash once the tag has been created and pushed"
📣 @NajiNazzal! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
Format:
Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>
Activity
roryabraham commentedon Jan 4, 2022
We've seen similar problem that suggests a similar solution to this, namely: "Only update the app version on the
StagingDeployCashonce the tag has been created and pushed"roryabraham commentedon Jan 18, 2022
No update here
roryabraham commentedon Jan 29, 2022
Another good improvement to make once pascalgn/automerge-action#177 is merged would be to delete the unmerged PR branch if the automerge-action fails.
52 remaining items
melvin-bot commentedon Jun 5, 2023
@roryabraham, this Monthly task hasn't been acted upon in 6 weeks; closing.
If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.
NajiNazzal commentedon Aug 7, 2023
Can I register?
melvin-bot commentedon Aug 7, 2023
📣 @NajiNazzal! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:
Format:
NajiNazzal commentedon Aug 7, 2023
Contributor details
Your Expensify account email: najinazzal98@gmail.com
Upwork Profile Link: https://www.upwork.com/freelancers/~01a352a7b4bf7c67cd
melvin-bot commentedon Aug 7, 2023
✅ Contributor details stored successfully. Thank you for contributing to Expensify!
melvin-bot commentedon Aug 21, 2023
@roryabraham, this Monthly task hasn't been acted upon in 6 weeks; closing.
If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.
melvin-bot commentedon Nov 20, 2023
@roryabraham, this Monthly task hasn't been acted upon in 6 weeks; closing.
If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.