Update to the stiging branch and create a new branch off of it. Then close the old branch. In summary: hg update stiging hg branch staging hg commit -m”Changing stiging branch to staging.” hg update stiging hg commit –close-branch -m”This was a typo; use staging instead.” hg push –new-branch
With the release of Mercurial 2.2, you can use the –amend option with hg commit to update the last commit with the current working directory From the command line reference: The –amend flag can be used to amend the parent of the working directory with a new commit that contains the changes in the parent … Read more
Enable the “strip” extension and type the following: hg strip #changeset# –keep Where #changeset# is the hash for the changeset you want to remove. This will remove the said changeset including changesets that descend from it and will leave your working directory untouched. If you wish to also revert your committed code changes remove the … Read more
Add the Mercurial Extension called purge. It is distributed by Mercurial. This extension adds a “purge” command to “hg” that removes files not known to Mercurial. i.e. untracked Files. So your command would be, hg purge It is not enabled by default, maybe to avoid accidentally removing files that you forgot to add. To install … Read more
As shown in the docs, all you should need to do is just click on the branch: default button near the top of the commit dialog, and change to a new branch name.
This will add all new files that are not ignored, and remove all locally missing files hg addremove Either of these will remove all locally missing files(They are the same command) hg remove –after hg remove -A
You can make an auth section in your .hgrc or Mercurial.ini file, like so: [auth] bb.prefix = https://bitbucket.org/repo/path bb.username = foo bb.password = foo_passwd The ‘bb’ part is an arbitrary identifier and is used to match prefix with username and password – handy for managing different username/password combos with different sites (prefix) You can also … Read more
When “waiting for lock on repository”, delete the repository file: .hg/wlock (or it may be in .hg/store/lock) When deleting the lock file, you must make sure nothing else is accessing the repository. (If the lock is a string of zeros or blank, this is almost certainly true).