Admin note: Moved from [Beta] Do not AutoCommit changes - #11
This request seemed to be (partially?) implemented in the Beta editor for me yesterday. I noticed that (sometimes, at least) if I started editing from a previously auto-saved commit, I would find myself “editing” that commit rather than working on a new commit. So I would have a chance to name the commit when finished, and the old auto-saved name would be gone from the commit history.
However, in at least one instance, I’m pretty sure a manually-named commit was overwritten in this way, which was a little scary. The changes were not lost, but they got combined into what I had intended to be a distinct, subsequent commit.
edit: Something like this happened again just now , but (this time, at least) there was more to it than I previously realized. Here’s the git history I ended up with: (The requests branch and the commit tagged ‘anvil-preserved/128’ are irrelevant to my story, and you can also ignore the published branch.)
Here’s how I got there:
- Working on the master branch, I manually saved the “Reduce MatchForm doorbell volume” commit.
- Then I manually saved the “Add MobileAlert note re ping” commit.
- Deciding to abandon that commit, I right-clicked on the “Reduce MatchForm doorbell volume” commit and selected “Reset ‘master’ branch to here.”
- Then I started making a new change in the IDE. When I went to commit the changes, I found that the “Reduce MatchForm doorbell volume” change was now included in the current “editing” commit. At first I thought that commit message had been lost, squashed into the current “editing” commit. So I included note of it in my new commit message. (I then noticed the original doorbell commit message had been preserved in an abandoned branch marked ‘anvil-preserved/129’. To reiterate, I am 100% sure I did not re-make the doorbell volume change after step 3. But for some reason, the IDE decided to rearrange things in this way.)