Yes, the right way is to use --git-committer-email and
--git-committer-name. The reason we have them as flags instead of a
config value or even more dynamic, allowed to change it per commit, is
that the committer shouldn't really change per commit. That is why git
differentiates between author and commiter:
- Author: who created the change
- committer: How was in charge of putting the change in the repo.
In this case "copybara" or the current user running the workflow is
the best choice. Internally we use it like that, in the CLI, it uses
the current user that runs the migration. In the internal service we
have, we overwrite (or let overwrite per project) using those flags,
to mark that it was done in the service.
I hope it helps.
> --
> You received this message because you are subscribed to the Google Groups "Copybara OSS" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
copybara-discu...@googlegroups.com.
> To view this discussion on the web visit
https://groups.google.com/d/msgid/copybara-discuss/3aa06e0c-bedd-4f07-a7cc-ac84cee46a6en%40googlegroups.com.