I suggest you ...

287 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mike-EEEMike-EEE shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    5 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Anonymous commented  ·   ·  Flag as inappropriate

        This is very sad, as it renders basically all IDEs (at least all of them using libgit2) unable to integrate with commit hooks workflows.

        The point of git commit hooks is that they are respected, not that they may ignored depending on the tool you use to interact with git.

      • BranoBrano commented  ·   ·  Flag as inappropriate

        The integration becomes useless for me then. We use CI builds and we need to notify Jenkins after each commit. :(

      • Virgil SchleichVirgil Schleich commented  ·   ·  Flag as inappropriate

        This is a great suggestion. The hooks are part of the standard Git implementation. I don't know why MS did not implement them.

        We are using a non-MS code review product that uses the post-commit hook to catch changes. Without VS executing these standard hooks, the VS integration is pretty much useless to us.

      Feedback and Knowledge Base