Understanding the workflow

[Farid Zakaria]

Hello!

I'd like to understand the workflow for how people use copybara with `git_destination`.

I can't understand a workflow that immediately pushes the changes to the remote repository before you've: had a chance to review or had someone else to review.

I see there is an option to create a pull_request as well which I plan to play with but I was hoping to understand if I was just _missing_ some key piece of the workflow.

My ideal / current workflow: I happen to always pick folder destination so that I can iterate (re-apply copybara multiple times) and then push the git commit / PR myself.

Is what is missing hand-adding the RevId to get into a state of bliss through this workflow?
(I don't mind not having the history, I am pulling in third_party code into a sub-folder)

I tried to scour the group/github to find some beefier examples/explanations and came up short. Happy to also take links to anything I might of missed.

Thanks :)