You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This tracking issue covers the various design polish items we want to implement across both web and mobile. See Slack (internal) for more context on this project.
Is it okay for you to be a co-author but also a PR approver?
@shawnborton In the MelvinBot workflow, C+ should be added as a co-author so we can provide feedback and request updates directly after reviewing.
For the current bugs, once we agree on and approve Melvin’s proposal, Melvin creates the PR and assigns the C+ as a co-author to review and provide feedback. If we’re only reviewers, MelvinBot won’t be able to implement our feedback directly. We would have to wait for you to assign the implementation to Melvin, which adds an extra step and takes more time. It would be more efficient if C+ could be a co-author and provide feedback directly to MelvinBot.
Totally, I get where you are coming from and I see where this makes life much easier for you as a reviewer! I just want to check internally to make sure this is expected and okay.
@shawnborton@grgia I’ve finished reviewing these 4 PRs and left feedback for MelvinBot to update. They’ve been approved and are ready for your final review and merge:
I also looked through these 2 PRs, but they don’t seem ready yet. I’ve asked @grgia and @shawnborton to take a look. Please tag me when they’re ready for another review:
Activity
grgia commentedon Sep 10, 2026
🤟 Rad
1 remaining item
shawnborton commentedon Sep 11, 2026
Is it okay for you to be a co-author but also a PR approver?
huult commentedon Sep 11, 2026
@shawnborton In the MelvinBot workflow, C+ should be added as a co-author so we can provide feedback and request updates directly after reviewing.
For the current bugs, once we agree on and approve Melvin’s proposal, Melvin creates the PR and assigns the C+ as a co-author to review and provide feedback. If we’re only reviewers, MelvinBot won’t be able to implement our feedback directly. We would have to wait for you to assign the implementation to Melvin, which adds an extra step and takes more time. It would be more efficient if C+ could be a co-author and provide feedback directly to MelvinBot.
shawnborton commentedon Sep 11, 2026
Okay cool, let's get a quick confirmation from @grgia - I thought we never wanted the reviewer to also be a PR author per our compliance policies.
huult commentedon Sep 11, 2026
@shawnborton For example, here are PRs #100360 and #100672 where I worked with MelvinBot. 😄
shawnborton commentedon Sep 11, 2026
Totally, I get where you are coming from and I see where this makes life much easier for you as a reviewer! I just want to check internally to make sure this is expected and okay.
huult commentedon Sep 11, 2026
Yeah, totally agree. While we’re waiting for confirmation, I’ll continue reviewing and providing feedback.
grgia commentedon Sep 11, 2026
@shawnborton @huult it's technically fine so long as there is one employee non-author review
shawnborton commentedon Sep 11, 2026
Great! @huult going to assign you to the PRs then
huult commentedon Sep 14, 2026
@shawnborton @grgia I’ve finished reviewing these 4 PRs and left feedback for MelvinBot to update. They’ve been approved and are ready for your final review and merge:
#100817
#100832
#100805
#100835
#100881
#100831
I also looked through these 2 PRs, but they don’t seem ready yet. I’ve asked @grgia and @shawnborton to take a look. Please tag me when they’re ready for another review:#100881 -> @grgia #100881 (comment)#100831 -> @shawnborton #100831 (comment)shawnborton commentedon Sep 14, 2026
Sounds good, responded to or merged the PRs above.