Using a file template is definitely the best solution. For example, if you have a database.ini file, commit a database.ini.template file and ignore ...
all listed could distract us from changes that actually matter, so let's tell Mercurial to ignore them.
hgignore , but Mercurial still notices modifications. Can I have a file "tracked" in a Mercurial repository, yet ignore future local changes to that file ...
File is being tracked by mercurial but you don't want to commit changes - no solution.
You can track changes to projects and individual files with RSS feeds from hgweb. Here are
After you hg remove a file, Mercurial will no longer track changes to that file,
not tracked I = ignored = origin of the previous file (with --copies).
Now it's time to tell Mercurial which files must be tracked.
A tracked file with changes is automatically added to a commit.
Your project will have a repository for hg to track files. There are two ways