Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove .gitattributes files from vendor directory #4824

Merged

Conversation

saschagrunert
Copy link
Member

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

.gitattributes files containing export-subst will cause that the
source code tarball contents will change when the short commit does. To
avoid that we now ignore .gitattributes files from the vendor directory.

Which issue(s) this PR fixes:

Fixes #4820

Special notes for your reviewer:

None

Does this PR introduce a user-facing change?

None

@openshift-ci-robot openshift-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Apr 29, 2021
@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

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 Apr 29, 2021
.gitattributes files containing `export-subst` will cause that the
source code tarball  contents will change when the short commit does. To
avoid that we now ignore .gitattributes files from the vendor directory.

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
@codecov
Copy link

codecov bot commented Apr 29, 2021

Codecov Report

Merging #4824 (dbca042) into master (ce8057c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #4824   +/-   ##
=======================================
  Coverage   43.00%   43.00%           
=======================================
  Files         107      107           
  Lines        9792     9792           
=======================================
  Hits         4211     4211           
  Misses       5131     5131           
  Partials      450      450           

@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 Apr 29, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 29, 2021

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

Test name Commit Details Rerun command
ci/openshift-jenkins/e2e_crun_cgroupv2 dbca042 link /test e2e_cgroupv2

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.

@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@saschagrunert
Copy link
Member Author

/override ci/prow/e2e-gcp

@openshift-ci-robot
Copy link

@saschagrunert: Overrode contexts on behalf of saschagrunert: ci/prow/e2e-gcp

In response to this:

/override ci/prow/e2e-gcp

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 openshift-merge-robot merged commit 1bf9478 into cri-o:master Apr 29, 2021
@saschagrunert saschagrunert deleted the vendor-gitattributes branch April 29, 2021 15:10
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/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. 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.

The checksum of the source archive keeps changing
5 participants