MERCURIAL WINDOWS HOOK ON LOCAL COMMIT ADD COMMENT KEYGEN
Run once for each new changeset that is brought into the
Run after a new changeset has been created in the local Is run after a group of changesets has been brought into the “ triggers” in some revision control systems, but the The name Mercurial uses for one of these actions is a In some cases, you can even control Mercurial's Mercurial offers a powerful mechanism to let you performĪutomated actions in response to events that occur in a
Updating or merging working directory tag-after tagging a Tagging a changeset pretxnchangegroup-beforeĬompleting addition of remote changesets pretxncommit-beforeĬompleting commit of new changeset preupdate-before Starting to propagate changesets pretag-before Starting to commit a changeset preoutgoing-before To add remote changesets precommit-before Remote changesets added commit-after a newĬhangesets are propagated prechangegroup-before starting Hook Testing and troubleshooting Information for writers of hooks In-process hook execution External hook execution Finding out where changesets come from Sources of changesets Where changes are going-remote repository Hook Mapping committer names to Bugzilla user names Configuring the text that gets added to a bug Testing and troubleshooting notify-send email Hook Testing and troubleshooting bugzilla-integration with Table of Contents An overview of hooks in Mercurial Hooks and security Hooks are run with your privileges Hooks do not propagate Hooks can be overridden Ensuring that critical hooks are run A short tutorial on using hooks Performing multiple actions per event Controlling whether an activity can proceed Writing your own hooks Choosing how your hook should run Hook parameters Hook return values and activity control Writing an external hook Telling Mercurial to use an in-process hook Writing an in-process hook Some hook examples Writing meaningful commit messages Checking for trailing whitespace Bundled hooks acl-accessĬontrol for parts of a repository Configuring the acl
0 kommentar(er)
