This is a stub issue - GH sync v2 hasn't been fully specced out yet
In short, the idea of GH sync is that you sync a whole GH repo to a Lightning workspace. each project/sandbox to its own branch (and you can set up other instances on branches too).
I just wanted to save a reminder here: when setting up sync, we should allow a direction. By default sync is 2 way. But for example on your production instance you don;'t want a 2 way sync - if someone changes a workflow in prod we don't want to accidentally pull the change back to main and trigger all sorts of conflicts.
This is a stub issue - GH sync v2 hasn't been fully specced out yet
In short, the idea of GH sync is that you sync a whole GH repo to a Lightning workspace. each project/sandbox to its own branch (and you can set up other instances on branches too).
I just wanted to save a reminder here: when setting up sync, we should allow a direction. By default sync is 2 way. But for example on your production instance you don;'t want a 2 way sync - if someone changes a workflow in prod we don't want to accidentally pull the change back to main and trigger all sorts of conflicts.