-
Notifications
You must be signed in to change notification settings - Fork 3.5k
[No QA] Update botify workflows to use new signing key #6374
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
Conversation
|
|
| - name: Set up git for Botify | ||
| if: github.actor == 'OSBotify' | ||
| run: | | ||
| git config user.signingkey DBF63700F60F5530 |
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.
Does this signingkey need to be stored as an environment variable?
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.
Co-authored-by: Andrew Gable <andrew@expensify.com>
|
Skipping E2E tests to unblock CPs. |
|
@AndrewGable looks like this was merged without passing tests. Please add a note explaining why this was done and remove the |
|
🚀 Deployed to staging by @AndrewGable in version: 1.1.15-18 🚀
|
|
🚀 Deployed to production by @roryabraham in version: 1.1.16-10 🚀
|

Details
#6371 fixed the issue with the createNewVersion workflow, but the cherry-pick workflow failed. This PR updates all botify flows that push to git to use the updated signing key.
A future improvement here would be to create a separate workflow to handle setting up the git config for botify to reduce duplicate code, so once CPs are fixed we can create a follow-up issue to do that.
Fixed Issues
Fixes broken GH action
Tests
Merge and CP this, confirm the workflow is successful and that the commits are signed.
QA Steps
None
Tested On
Screenshots
Web
Mobile Web
Desktop
iOS
Android