+Author: [Alan Franzoni](www.franzoni.eu)
+Project Homepage: [http://hgskipcommit.franzoni.eu](http://hgskipcommit.franzoni.eu)
+Mercurial extension that allows to skip some files when committing, something like "ignore on commit".
+Even though it would be better to commit a template on a vcs - that
+every user or developer can then copy and customize, there are some situations
+where that's not possible, mostly because some externally managed software
+(e.g. a library, framework, or IDE) insists on using or modifying certain
+If developers, then, inadvertently modify and commit such files, many problem
+This extension provides a simple way to prevent it; if a "wild commit" (i.e. a
+commit without file selection) occurs, any file matching the hgskipcommit
+pattern won't get committed, and will just stay modified on the repo.
+Ehenever a commit without file selection is issued, the hgskipcommit pattern is
+taken into account and just added to the 'exclude' options for commit; the very
+same functionality can be achieved via command line -X option.
+If at least one target file to be committed is passed on the command line this
+extension performs no action.
+after cloning the repo or getting the tarball, edit your $HOME/.hgrc, and enable the extension:
+Configuration, just like any mercurial config value, can be done system-wide,
+per user, or per repo. In the hgrc you choose, just add the section and
+configure the pattern value.
+Small notice: at the time of this writing, patterns are not additive; anything
+specified in an higher priority config file just overrides the lower priority
+setting. Priority in descending order is repo -> user -> system.
+Skip committing config files from the most well-known IDEs, since
+they often pollute commits
+ pattern = path:.idea path:nbproject path:.project path:.settings path:*.iml
+pattern syntax just follows [mercurial patterns](http://www.selenic.com/mercurial/hg.1.html#file-name-patterns) - see `hg help patterns'
+Be aware that setting an absolute exclude (relative to repository root) will
+probably require a path: or re: file pattern, otherwise it'll be interpreted as
+an exclude relative to the current directory.
+### current status and known issues
+coCfiguration is currently handled as extensions configuration, so it's not
+shared between repositories. If there're requests I may make a change and adopt
+an .hgignore like approach that could be shared between repositories.