Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-3026

git-hook didnt trigger if we promote changes from one branch to other.

XMLWordPrintable

    • CR1
    • +
    • Hide
      • Create Project with multiple branches like, develop and master
      • Configure git-hook to push changes from master branch.
      •  post-commit file look like as:
      #!/bin/sh
git push origin master
      •  Create any asset in develop branch and merge the changes to master  through 'Change Request' tab from BC console.
      • Once changes are merged in master branch, git-hook should be triggered, but it didnt trigger.
      • If we open any asset and click on 'Save' button then githook is triggered but it should also be triggered when changes are murged.
      Show
      Create Project with multiple branches like, develop and master Configure git-hook to push changes from master branch.  post-commit file look like as: #!/bin/sh git push origin master  Create any asset in develop branch and merge the changes to master  through 'Change Request' tab from BC console. Once changes are merged in master branch, git-hook should be triggered, but it didnt trigger. If we open any asset and click on 'Save' button then githook is triggered but it should also be triggered when changes are murged.

      If user made a change in Develop branch and merges the changes to Master branch on BC side, this does not get propagated to remote git repository through configured git-hook.

              r_anand Rishiraj Anand (Inactive)
              rhn-support-abhumbe Abhijit Humbe
              Srihari V Srihari V
              Srihari V Srihari V
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: