Skip to content

Update git-blame-ignore-revs following new ufmt version #6303

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

Merged
merged 2 commits into from
Jul 22, 2022

Conversation

NicolasHug
Copy link
Member

This will help ignoring #5106 in git blame.

I also updated our CONTRIBUTING guide instruction regarding the required version of black, etc.

@NicolasHug NicolasHug added code quality other if you have no clue or if you will manually handle the PR in the release notes labels Jul 22, 2022
@vfdev-5
Copy link
Collaborator

vfdev-5 commented Jul 22, 2022

@NicolasHug please update ufmt version here as well :

- repo: https://github.com/omnilib/ufmt
rev: v1.3.2


This comment is irrelevant

@NicolasHug
Copy link
Member Author

Sorry I got mixed-up myself. The ufmt version didn't change (my comment in your other PR was wrong). Fixed now!

Copy link
Collaborator

@vfdev-5 vfdev-5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm :)

@NicolasHug NicolasHug merged commit 9b84859 into pytorch:main Jul 22, 2022
@github-actions
Copy link

Hey @NicolasHug!

You merged this PR, but no labels were added. The list of valid labels is available at https://github.com/pytorch/vision/blob/main/.github/process_commit.py

facebook-github-bot pushed a commit that referenced this pull request Jul 28, 2022
Summary:
* Update git-blame-ignore-revs following new ufmt version

* Un-do ufmt version changed, got mixed up

Reviewed By: datumbox

Differential Revision: D38154571

fbshipit-source-id: 8c59716538a3051aabc7cd531e3edf04fcc9e360
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla signed code quality other if you have no clue or if you will manually handle the PR in the release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants