-
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
[Payment due][$500] Implement Uneven Splits #40616
Comments
PR should be ready for review first thing Monday morning. |
More progress is done in the PR, I'm resolving one final issue here |
|
Heads up: C+ payout for this one should be $500. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as off-topic.
This comment was marked as off-topic.
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
This is done! |
@youssef-lr I was the C+ for the PR and reviewed and tested it. Could you please reopen this for payment? |
Done, sorry! |
Thanks. I think Bug and Daily labels need to be added for assigning a BZ member for payment. |
Will do on Monday. |
@youssef-lr gentle bump on this |
Triggered auto assignment to @kadiealexander ( |
@kadiealexander can we please issue payment for @c3024? Thanks! |
Job added to Upwork: https://www.upwork.com/jobs/~012b261d8e3721b659 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @shubham1206agra ( |
@kadiealexander applied, thanks. But the Upwork job price is shown as only $250. This is a $500 issue. |
Fixed. |
Applied! |
Thanks, accepted the offer! |
Implement this section of the design doc.
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @kadiealexanderThe text was updated successfully, but these errors were encountered: