-
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
[No QA]Generate a new GPG key and add it to the .gitignore
#6957
Conversation
|
||
# GitHub GPG Keys | ||
.github/workflows/OSBotify-private-key.asc | ||
*.asc |
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.
FYI - I verified via find . -name "*.asc"
that there are no other keys that would be unintentionally ignored via this.
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.
NAB: Just wondering if .github/workflows/OSBotify-private-key.asc
is already included in *.asc
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.
It should be yes, but this is somewhat a safety net just in case we ever change the name of the key. I could remove .github/workflows/OSBotify-private-key.asc
if it's too redundant.
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.
I guess I was double checking that it was intentional, I'm ok if you want to leave it there to be more explicit as it doesn't cause any problem :P, changing my comment to NAB.
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.
I think it's ok to leave it
.gitignore
.gitignore
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.
I didn't find any missed DBF63700F60F5530
to replace. Changes look good to me!
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
|
||
# GitHub GPG Keys | ||
.github/workflows/OSBotify-private-key.asc | ||
*.asc |
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.
I think it's ok to leave it
@rafecolton added GPG key on the GitHub side, going to merge and test. |
@AndrewGable looks like this was merged without passing tests. Please add a note explaining why this was done and remove the |
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
🚀 Deployed to staging by @AndrewGable in version: 1.1.24-19 🚀
|
🚀 Deployed to production by @francoisl in version: 1.1.24-19 🚀
|
Details
367811D53E34168C
)App/.github/workflows/OSBotify-private-key.asc.gpg
.gitignore
.github/workflows/OSBotify-private-key.asc
and*.asc
to prevent the key from being exposed in future cherry pick PRs with conflicts.Fixed Issues
$ https://github.com/Expensify/Expensify/issues/190171
Tests
QA Steps
N/A