-
Notifications
You must be signed in to change notification settings - Fork 3k
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
🍒 Cherry pick PR #8011 to staging 🍒 #8013
Conversation
This pull request has merge conflicts and can not be automatically merged. 😞 |
The bit of code change looks good, but I'd feel better if there was someone more familiar with the new dot deploy to make sure the version stuff check sout |
Something weird happened here, be careful @danieldoglas. I'm not seeing any conflicts, but typically what happens if an auto-generated PR has conflicts is that we commit the conflicts, including the I'm very suspicious in this case because I don't see any conflicts. I'm not sure what happened here except that this line failed for some reason. |
@roryabraham sorry, I think I'm missing something. There was a conflict commited, which I manually solved and commited, so it seems like the right flow, right? |
Oh, completely missed the fact that you manually resolved conflicts. :oh_nothing: So you did everything right and I've just got a case of the Mondays. ignore me... |
@TomatoToaster for review since these changes were originally yours. |
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.
LGTM
🚀 Cherry-picked to staging by @TomatoToaster in version: 1.1.41-5 🚀
@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes. |
That's strange. That was not a conflict for me. |
🚀 Deployed to production by @francoisl in version: 1.1.41-6 🚀
|
🍒 Cherry pick #8011 to staging 🍒