Fair enough! I only have a single development machine, so that advantage was invisible for me - but that makes sense! You could theoretically get the benefits

Fair enough! I only have a single development machine, so that advantage was invisible for me - but that makes sense! You could theoretically get the benefits of both approaches, though: have your own personal repo to which you push "in-progress" commits for durability and portability, but maintain Amazon's tooling which generates PRs with a diff between a _local_ commit and the target (by, behind the scenes, generating the ephemeral fork from which to Request a Pull), and permitting updates to that PR from local (not necessarily "pushed to an online repo") commits. That's _still_ advantageous over GitHub's model, because: * If you don't want to have a personal repo, you don't have to * Even if you do, the process of updating a PR is simpler and more flexible when executed purely with local Git commands rather than by manipulating a remote repo I appreciate the perspective, thank you!