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
I believe right now when doing a review through the CLI the who line is derived from git with name and email? Believe this is a good default but it would be nice to be able to override it for example with an environment variable so one can route it differently without having to edit the review after the fact.
For example we at Embark (audits) don't use our personal or work emails for the reviews, instead preferring to us our public mailing list of opensource@embark-studios.com as a central contact point.
Could for example have optional env vars for overriding the who user name and email, potentially called something like CARGO_VET_USER and CARGO_VET_EMAIL that if available replaces the git user info.
If aligned, I can probably implement and add such support in a PR.
The text was updated successfully, but these errors were encountered:
I believe right now when doing a review through the CLI the
who
line is derived from git with name and email? Believe this is a good default but it would be nice to be able to override it for example with an environment variable so one can route it differently without having to edit the review after the fact.For example we at Embark (audits) don't use our personal or work emails for the reviews, instead preferring to us our public mailing list of
opensource@embark-studios.com
as a central contact point.Could for example have optional env vars for overriding the
who
user name and email, potentially called something likeCARGO_VET_USER
andCARGO_VET_EMAIL
that if available replaces the git user info.If aligned, I can probably implement and add such support in a PR.
The text was updated successfully, but these errors were encountered: