In our Workflow, persons from outside the tech-tea...
# how-do-i
a
In our Workflow, persons from outside the tech-team open PR for small wording changes from time to time (mainly using the GitHub UI). We would like to put those changes to the merge queue as well, to avoid interfering with the regular merges from our tech-team. Unfortunately when we attempt to put those items on the merge queue, we get an “Unknown error”. When I try to put the item on the merge queue using the GitHub labels, I get the error that the non-tech person does not have a Graphite Seat and therefor the label is removed. What is the recommended way for such a workflow? Is it really necessary to have fully paid Seats for all team-members that only commit every one or two months.
p
(If applicable) To help us more clearly understand what you're trying to do, please provide additional details about: - Screenshots / debug logs / list of commands you've tried to run so far - Your workflow - Current state
✅ 1
a
Our current workaround is to: a) get lucky with having a branch that is up to date with main and all CI checks are completed, then we can just merge into main. or b) force merge with overwriting our branch protection rules. Neither are great, and a) is especially difficult because we have so many changes pushed to main every day, that it’s very unlikely to hit this state.
p
Hey Adrian, yes the author of the PR needs to have a Graphite account for this to work today for non enterprise plans. The
unknown error
is caused by the same limitation.
a
Are there any plans to change that? We have 2x more people that from time to time that create such PRs for us, than we have developers, but it’s less than 1% of all PRs (about 1 per week). Having a Graphite Account with a fully paid seat for all of these people is not really an option, just for allowing them to open 5 PRs per year and not even merging it themself. Even if I as a developer make changes on their PR, and another developer approves it, we can’t use the merge queue. Maybe there should be a way to “adopt” a PR?
p
Thanks for the context, Adrian. Regarding "adopting" a PR, GitHub does not currently support transferring ownership of a PR so im not sure its something we would be able to implement.
a
Maybe it would be possible to check if someone with a graphite account was involved in the last (or any) commit of a PR?
p
I have captured this as an enhancement request.
a
Thank you!