With with Mercurial queues extension, I can make an empty commit with some commit message like so:
hg qnew patch_name -m "message"
Is there a way to do this without Mercurial queues? I tried simply:
hg commit -m "message"
but hg just says "nothing changed" and doesn't do the commit, and I don't see any "force" option that would override that.
If you're wondering about my motivation for doing this: we have testing infrastructure where you push to a special repository and it will trigger automated tests to run. You need to put a special string into the commit message of the tipmost commit that says which tests to run. Obviously, I don't want this string in there when I push to the actual repository. Rather than amending the commit twice (once to add the special string, and a second time to remove it), I would find it cleaner to just add an empty commit, and then roll it back -- and I can do this with mq, but I'd like to find a way to do it without mq.
Pushing an empty commit without adding any staged files to the branch is very easy. It is the same as pushing a regular commit, except that all you need to do is add –allow-empty flag to the command line. The commit is now pushed to your branch without any changes.
Like --allow-empty this command is primarily for use by foreign SCM interface scripts. It allows you to create a commit with an empty commit message without using plumbing commands like git-commit-tree[1].
If you are still in the draft phase (not pushed elsewhere yet), use the built-in extension hg strip <rev> command. Otherwise, you should do a hg backout , which will reverse the changeset. In case you still need the commit you made, I suggest you export it to import it again in the correct branch, before stripping.
Since version 2.2, the commit command has a --amend option that will fold any changes into your working directory into the latest commit, and allow you to edit the commit message. hg commit --amend can in fact be used on any changeset that is a (topological) branch head, that is, one that has no child changesets.
You can use hg commit --amend
to create empty commits.
Just create an arbitrary commit and backout the change. Afterwards fold both commits together.
Example:
touch tmp # create dummy file
hg add tmp # add file and...
hg commit -m "tmp" # ... commit
hg rm tmp # remove the file again and ...
hg commit --amend -m "empty commit" # ... commit
You can make commit that's closing the branch:
hg commit --close-branch -m "message"
Update:
You can close branch once, but it can be reopened with another commit. Simplest way to reopen branch without changing files is to tag some revision. So you can use hg commit --close-branch
for empty commit and then hg tag
for reopening.
Update v2
Actually you can create new empty commits with just hg tag
command. It has -m
parameter for setting a commit message. If you don't really care about correctness of this tags, you can use just one tag name by calling hg tag
with -f
parameter:
hg tag t1 -f -m "message"
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With