Fix downstream commit detection #69
Conversation
In some cases, upstream commits were included in the git log command, causing the verify-git-history test to fail because the commits did not follow name rules.
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JoelSpeed The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
@RadekManak: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/label jira/valid-bug |
openshift-ci
bot
added
the
jira/valid-bug
|
/override ci/prow/e2e-azure-ovn This PR has zero effect on the payload, so no need to run E2E |
|
@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/e2e-azure-ovn, ci/prow/e2e-azure-ovn-upgrade In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
openshift-merge-robot
merged commit 9b7ee37
into
openshift:master
In some cases, upstream commits were included in the git log command, causing the verify-git-history test to fail because the commits did not follow name rules.