-
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
[Pay on 3/20]Payment issue for E/App PR#38096 #38105
Comments
Job added to Upwork: https://www.upwork.com/jobs/~01e863ba97b98f2a8e |
Current assignee @mkhutornyi is eligible for the Internal assigner, not assigning anyone new. |
Triggered auto assignment to @mallenexpensify ( |
@mallenexpensify, @mkhutornyi Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@mkhutornyi can you please accept the job and reply here once you have? |
@mkhutornyi can you please accept the job and reply here once you have? |
@mallenexpensify, @mkhutornyi Eep! 4 days overdue now. Issues have feelings too... |
Looks like @mkhutornyi is out sick. |
@mallenexpensify, @mkhutornyi Eep! 4 days overdue now. Issues have feelings too... |
@mkhutornyi can you comment here when you're back? bumping to monthly |
@mkhutornyi , you're back, right? bumping to daily and marking you as owner. |
yes, can you please send new offer? |
@mkhutornyi , can you please accept the job and reply here once you have? Can you check to see if there are other issues you're due payment for? If so, comment on them. If they're not getting 👀 and responses (ie. if they're closed), wait a few days then post in #contributor-plus with a list of links to issues and cc me in the post |
Contributor+: @mkhutornyi paid $500 via Upwork. |
Issue created to compensate the Contributor+ member for their work on #38096
E/E issue linked to the PR - no internal issue.
Contributor+ member who reviewed the PR - @mkhutornyi.
Wait 7 days after the PR is deployed to production before issuing payment in case there are regressions.
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @mkhutornyiThe text was updated successfully, but these errors were encountered: