[v5,0/7] git-p4: add hooks for p4-changelist

Message

Koji Nakamaru via GitGitGadget Feb. 11, 2020, 6:57 p.m. UTC

Request for help - if there are any experts with python and Windows, I would
appreciate a review of the changes that I have presented here.


----------------------------------------------------------------------------

Our company's workflow requires that our P4 check-in messages have a
specific format. A helpful feature in the GIT-P4 program would be a hook
that occurs after the P4 change list is created but before it is displayed
in the editor that would allow an external program to possibly edit the
changelist text.

v1:My suggestion for the hook name is p4-pre-edit-changelist.

It would take a single parameter, the full path of the temporary file. If
the hook returns a non-zero exit code, it would cancel the current P4
submit.

The hook should be optional.

v2:Instead of a single hook, p4-pre-edit-changelist, follow the git
convention for hook names and add the trio of hooks that work together,
similar to git commit.

The hook names are: 

 * p4-prepare-changelist
 * p4-changelist
 * p4-post-changelist

The hooks should follow the same convention as git commit, so a new command
line option for the git-p4 submit function --no-verify should also be added.

v3:2-Feb-2020 This version reorganizes the commits to be easier to read. The
function for running the git hook has been rewritten to include suggestions.
This version no longer restricts the executable supported by windows for the
hook. It will first look for a file with the hook name without an extension
and if found, it will pass it to sh.exe (Git for Window's MINGW shell)
Otherwise it will take the file with the lowest alphabetical extension and
ask Windows to execute the program.

v3:10-Feb-2020 Integrated the suggested changes from the mailing list into
this release. The changes are:

 * Restructure the commits to pull the p4-pre-submit hook changes into the
   commit for adding git_run_hook.
 * Update the git_run_hook to include additional tests for GIT_DIR being set
   if getting the environment returns no value.
 * Updated the windows file resolution to ensure that the script to be run
   is NOT the .SAMPLE version of the hooks.
 * Split the RCS keyword cleanup message into its own commit.

Thank you in advance!

Ben Keene (7):
  git-p4: rewrite prompt to be Windows compatible
  git-p4: create new function run_git_hook
  git-p4: add p4-pre-submit exit text
  git-p4: add --no-verify option
  git-p4: restructure code in submit
  git-p4: add p4 submit hooks
  git-p4: add RCS keyword status message

 Documentation/git-p4.txt   |  45 ++++++-
 Documentation/githooks.txt |  51 +++++++-
 git-p4.py                  | 236 ++++++++++++++++++++++++++++---------
 3 files changed, 274 insertions(+), 58 deletions(-)


base-commit: de93cc14ab7e8db7645d8dbe4fd2603f76d5851f
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-698%2Fseraphire%2Fseraphire%2Fp4-hook-v5
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-698/seraphire/seraphire/p4-hook-v5
Pull-Request: https://github.com/git/git/pull/698

Range-diff vs v4:

 1:  71c51ccfb0 = 1:  71c51ccfb0 git-p4: rewrite prompt to be Windows compatible
 2:  596b18e5e5 ! 2:  a2342f7161 git-p4: create new function run_git_hook
     @@ -152,15 +152,7 @@
      -
      -        hook_file = os.path.join(hooks_path, "p4-pre-submit")
      -        if os.path.isfile(hook_file) and os.access(hook_file, os.X_OK) and subprocess.call([hook_file]) != 0:
     -+        try:
     -+            if not run_git_hook("p4-pre-submit"):
     -+                print("\nThe p4-pre-submit hook failed, aborting the submit.\n\nYou can skip " \
     -+                    "this pre-submission check by adding\nthe command line option '--no-verify', " \
     -+                    "however,\nthis will also skip the p4-changelist hook as well.")
     -+                sys.exit(1)
     -+        except Exception as e:
     -+            print("\nThe p4-pre-submit hook failed, aborting the submit.\n\nThe hook failed "\
     -+                "with the error '{0}'".format(e.message) )
     ++        if not run_git_hook("p4-pre-submit"):
                   sys.exit(1)
       
               #
 -:  ---------- > 3:  5f2b47bf6a git-p4: add p4-pre-submit exit text
 3:  57a6166ed1 ! 4:  05b8c7ad67 git-p4: add --no-verify option
     @@ -95,3 +95,30 @@
       
               if gitConfig('git-p4.largeFileSystem'):
                   die("Large file system not supported for git-p4 submit command. Please remove it from config.")
     +@@
     +             sys.exit("number of commits (%d) must match number of shelved changelist (%d)" %
     +                      (len(commits), num_shelves))
     + 
     +-        try:
     +-            if not run_git_hook("p4-pre-submit"):
     +-                print("\nThe p4-pre-submit hook failed, aborting the submit.\n\nYou can skip " \
     +-                    "this pre-submission check by adding\nthe command line option '--no-verify', " \
     +-                    "however,\nthis will also skip the p4-changelist hook as well.")
     ++        if not self.no_verify:
     ++            try:
     ++                if not run_git_hook("p4-pre-submit"):
     ++                    print("\nThe p4-pre-submit hook failed, aborting the submit.\n\nYou can skip " \
     ++                        "this pre-submission check by adding\nthe command line option '--no-verify', " \
     ++                        "however,\nthis will also skip the p4-changelist hook as well.")
     ++                    sys.exit(1)
     ++            except Exception as e:
     ++                print("\nThe p4-pre-submit hook failed, aborting the submit.\n\nThe hook failed "\
     ++                    "with the error '{0}'".format(e.message) )
     +                 sys.exit(1)
     +-        except Exception as e:
     +-            print("\nThe p4-pre-submit hook failed, aborting the submit.\n\nThe hook failed "\
     +-                "with the error '{0}'".format(e.message) )
     +-            sys.exit(1)
     + 
     +         #
     +         # Apply the commits, one at a time.  On failure, ask if should
 4:  d17e032767 = 5:  5299f61e4e git-p4: restructure code in submit
 5:  ceb2b0aff6 = 6:  7a6d9fafce git-p4: add p4 submit hooks
 6:  b92e017cb1 ! 7:  c0aca43185 git-4: add RCS keyword status message
     @@ -1,15 +1,15 @@
      Author: Ben Keene <[e-mail]>
      
     -    git-4: add RCS keyword status message
     +    git-p4: add RCS keyword status message
      
          During the p4 submit process, git-p4 will attempt to apply a patch
     -    to the files found in the p4 workspace. However, it P4 uses RCS
     +    to the files found in the p4 workspace. However, if P4 uses RCS
          keyword expansion, this patch may fail.
      
          When the patch fails, the user is alerted to the failure and that git-p4
          will attempt to clear the expanded text from the files and re-apply
          the patch. The current version of git-p4 does not tell the user the
     -    result of applying the patch after the RCS expansion has been removed
     +    result of the re-apply attempt after the RCS expansion has been removed
          which can be confusing.
      
          Add a new print statement after the git patch has been successfully