-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[NoQA] Updating the isExpensifyEmployee action #8010
Conversation
Also, I have asked in Slack about another possible problem, which could be that the OS_BOTIFY does not have read access to the |
Updated to check for engineering team, per Slack thread here. |
Kindly asking you @AndrewGable for review as we discussed it in Slack, but no urgency here. |
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, the only thing that you've to change is what andrew requested.
Yes, sorry for the delay, hindered with school today! Gonna have a look soon. |
Co-authored-by: Andrew Gable <andrew@expensify.com>
@chiragsalian @AndrewGable I have accepted the suggestion for |
Can we add more logs somehow? Or look in the action's repo for some help in investigation? |
@chiragsalian @AndrewGable Alright, this should finally work. Thank you for your review! Also thanks to @AndrewGable for proposing to use the lint for debugging, I did not know about this! Great to know :) |
|
||
newContributorWelcomeMessage: | ||
runs-on: ubuntu-latest | ||
needs: isExpensifyEmployee | ||
if: ${{ github.actor != 'OSBotify' && !fromJSON(needs.isExpensifyEmployee.outputs.isExpensifyEmployee) }} | ||
if: ${{ github.actor != 'OSBotify' && !fromJSON(needs.isExpensifyEmployee.outputs.IS_EXPENSIFY_EMPLOYEE) }} |
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.
Should this be an OR
instead of an AND
?
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.
OR
would let OSBotify
through no? OSBotify is not a member of the team so if it will be OR the other condition will always be true.
✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release. |
Thanks for your help and patience on this one 😅 |
🚀 Deployed to staging by @chiragsalian in version: 1.1.42-0 🚀
|
Was anything done to verify if this worked? The team is called Also, I had a contributor's first PR merged here yesterday and there was no welcome comment. See the job was skipped: https://github.com/Expensify/App/runs/5490903931?check_suite_focus=true |
@roryabraham yes, we run this in lint workflow to see what the output is and you can see it here where it works. I have printed out the contents of the But I see what is worng there: It seems the |
So I will need to use this step: |
Oh, nice catch. Send a PR and I will review 🙂 |
🚀 Deployed to production by @chiragsalian in version: 1.1.42-6 🚀
|
Details
We are trying to update the new contributor comment to only show when the contributor is the author of the PR. Currently, we show the comment for Expensify employees' first PR.
Although the job code is basically the same as here:
App/.github/workflows/cherryPick.yml
Lines 15 to 33 in 1a351d3
It seems it does not work as expected. The steps of the
newContributorWelcomeMessage
job are being run even for internal contributors, which should not happen.I am just trying out in this PR, whether the same name of the output variable as the job is not causing this issue, currently, I do not know why it does not work.
Fixed Issues
$ https://github.com/Expensify/Expensify/issues/194440
Tests
PR Review Checklist
Contributor (PR Author) Checklist
main
### Fixed Issues
section abovesrc/languages/*
files (if applicable)Styling.md
) for all style edits I madeSTYLE.md
)Avatar
, I verified the components usingAvatar
are working as expected)main
branch)PR Reviewer Checklist
main
### Fixed Issues
section abovesrc/languages/*
files (if applicable)STYLE.md
) were followedAvatar
, I verified the components usingAvatar
are working as expected)main
branch)QA Steps
I will take care of the QA. Same as here #7672