Skip to content

GitHub vs GitHub Enterprise in automerge - PR doesn't enter merged state #76

@mnuttall

Description

@mnuttall

Further to #75 investigate why GitHub Enterprise Pull Requests don't go into 'merged' state when a merge commit is pushed, leaving code in automerge-task.yaml of the form,

# On GitHub Enterprise - not GitHub.com - the issue will still be open. 
# We don't know if this is a bug or a feature. One way to work around this is with code of the form, 
# export GITHUB_HOST=github.ibm.com
# hub api -XPATCH repos/mnuttall/gitops-example-dev/pulls/4 -f state=closed
# See https://github.com/github/hub/issues/1151

If unavoidable, replace the commented out section above with working code that parses the PullRequest URL to generate the hub api -XPATCH command correctly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions