Geek Answers Handbook

Calculating frequent local commits with a push?

I recently switched to Mercurial from Subversion and was happy to learn about local commits .

However, I had a different workflow than I currently have.

I execute very frequent commits, i.e. my only push to the central repository includes 5-6 local commit changesets , each with their commit log . However, I would not want to see / return to these individual commits later in the future, but to my single push . I was hoping to see this push operation as an abstraction for my multiple local commits with one push log and all changes merged into one changeset .

+1
source share
2 answers

It depends a lot on what you want to achieve, but you can use the MQ extension to change the local commits (which MQ convert to patches) that you do first.

You can add two patches into one or update an existing patch by adding more changes.

There are two philosophies about which story is perfect:

  • fixations should be left intact, as they were made, or
  • history should contain fixations, as if they were made in an ideal world, by omniscient developers.

MQ works best if you like the latter approach.

+1
source

All commits are the same, there is no difference between "local" or "remote", and not with the computer on which they are stored.

Also, large commits (what you want to do) usually represent a bad idea and make understanding of changes difficult. Therefore, it is better to take early actions and perform often, as well as click on other developers (clicking does not mean merging!) So that they can use your code and merge when things need to be combined. If you are developing a broader functionality, you can also create branches, and when they end, merge them.

+2
source

More articles:


All Articles