Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@saschagrunert
Copy link
Member

What type of PR is this?

/kind dependency-change

What this PR does / why we need it:

The whitespace checks are mostly done by our linters and the DCO
verification will be done by prow. This means we can remove
git-validation if we agree on skipping the git commit message check.

Which issue(s) this PR fixes:

Refers to #4112

Special notes for your reviewer:

None

Does this PR introduce a user-facing change?

None

The whitespace checks are mostly done by our linters and the DCO
verification will be done by prow. This means we can remove
git-validation if we agree on skipping the git commit message check.

Signed-off-by: Sascha Grunert <[email protected]>
@openshift-ci-robot openshift-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/dependency-change Categorizes issue or PR as related to changing dependencies dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Aug 27, 2020
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: saschagrunert

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 27, 2020
@codecov
Copy link

codecov bot commented Aug 27, 2020

Codecov Report

Merging #4119 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #4119   +/-   ##
=======================================
  Coverage   40.35%   40.35%           
=======================================
  Files         110      110           
  Lines        9346     9346           
=======================================
  Hits         3772     3772           
  Misses       5223     5223           
  Partials      351      351           

@TomSweeneyRedHat
Copy link
Contributor

@saschagrunert for clarity, what does the "git commit message check" do/check?

@saschagrunert
Copy link
Member Author

@saschagrunert for clarity, what does the "git commit message check" do/check?

Just that the commit message subject is not longer than 90 characters.

@umohnani8
Copy link
Member

LGTM. I am fine with removing the 90 character check for the commit subject. @mrunalp @haircommander wdyt?

@haircommander
Copy link
Member

/retest
/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 3, 2020
@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 3, 2020

@saschagrunert: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/openshift-jenkins/e2e_crun_cgroupv2 7b942ed link /test e2e_cgroupv2
ci/prow/e2e-aws 7b942ed link /test e2e-aws

Full PR test history. Your PR dashboard.

Details

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.

@openshift-merge-robot openshift-merge-robot merged commit c2e44f8 into cri-o:master Sep 3, 2020
@saschagrunert saschagrunert deleted the git-validation branch September 3, 2020 17:29
@saschagrunert
Copy link
Member Author

/cherrypick release-1.19

@openshift-cherrypick-robot

@saschagrunert: new pull request created: #4169

Details

In response to this:

/cherrypick release-1.19

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. kind/dependency-change Categorizes issue or PR as related to changing dependencies lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants