Mercurial, unfortunately, does not clone the hook scripts when cloning a remote repository. These allow to verify when the developer commits a change, that may be well before he pushes that! Scripts executed by the hooks in the developers' local clones represent the earliest opportunity to verify commit policies. This feature is not available in the app yet, but we're seriously considering this. It is important to note that the earliest (thus best) opportunity to validate a commit policy would be in the developer's local clone repositories, using so-called client-side hooks. You can modify the rules any time, and those changes will be immediately reflected in all the repositories referencing them. This ensures that the rules are verified consistently in the blessed repository and all clones. ![]() When the hook script is installed to multiple repositories, all the hook scripts should verify the same policy. ![]() The sooner a commit gets rejected, the cheaper to fix it. Installing the hook scripts to these additional repositories will make your policies more efficient, as they are verified earlier in the process. In addition, you can also install the hook script to all the developer forks and in-between repositories. It is absolutely critical to verify the commit policy there. The blessed repository is the central hub for the developers, and it contains the reference source code. The hook script must be installed to the blessed repository, at least. The distributed nature of Mercurial allows you to select between multiple workflows.Īccordingly, you also have some flexibility in choosing where to install the hook scripts. Working with Mercurial commit policies Installing Mercurial commit hooks This page is about implementing Better Commit Policy with the Mercurial version control system.įor non-Mercurial-specific information, please see the starting page of the user manual.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |