Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 1838354
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 17, 20262026-05-17T06:28:00+00:00 2026-05-17T06:28:00+00:00

‘ve written two functions in a file commit_hooks.py that I want to run before

  • 0

‘ve written two functions in a file commit_hooks.py that I want to run before any commit is made persistent, but I can’t figure out how to write my hgrc to detect them.

The function headers are:

def precommit_bad_merge(ui, repo, parent1=None, parent2=None, **kwargs):
...

def precommit_bad_branching(ui, repo, **kwargs):
...

I’ve tried using this “guide“, but the documentation is too “man pagey” for me. The following is an outcast which doesn’t work.

[hooks]
precommit = ..\..\mno2\commit_hooks.py

Update!
Rewriting the hook line to:

precommit = D:\environments\next\mno2\commit_hooks.py

make Mercurial detect the precommit hook, but it always exits with status 1 for some reason.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-17T06:28:01+00:00Added an answer on May 17, 2026 at 6:28 am

    Set up your [hooks] section like this:

    [hooks]
    precommit.foo = python:D:\environments\next\mno2\commit_hooks.py:precommit_bad_merge
    precommit.bar = python:D:\environments\next\mno2\commit_hooks.py:precommit_bad_branching
    

    The syntax for the precommit line that you used is for external hooks, so it was treating your python file as a self-contained script (which I’m assuming it’s not since you’re using the function signatures for in-process hooks).

    You may need to have the python executable in your path (I do).

    For more information, see the definitive guide’s section on in-process hooks; there’s some useful information hidden in the comments.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.