gh stack sync fails in confusing ways if you are only tracking refs to master/main

[ahartwel]

Every time I used gh stack sync it would fail and require me to force push changes. I dug a bit and figured out that the ref tracking for my repo was in a wonky state and I wasn't tracking all refs on origin. After fixing my origin ref racking fetch = +refs/heads/*:refs/remotes/origin/* the problem went away and gh stack has been able to restack and manage my stack much more seamlessly.

It would be nice if gh stack was able to determine if my repo is configured in a way that breaks the tool and either prompt me to fix it or fix it itself.