Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
maint: Ignore formatting changes in history #3738
maint: Ignore formatting changes in history #3738
Changes from all commits
451c590
03c8480
406764f
bf298b1
f5a2529
4bc7889
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add the PR number like in the others? (some numbers are missing here and there below).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was no PR: 7f9c5ad
https://github.com/search?q=repo%3Amamba-org%2Fmamba+bump+clang-format+to+13.0.1&type=pullrequests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And I don't want to manually add PR numbers to other places - I don't see a lot of sense, and it will be more difficult to update this file later (more manual changes - less clear it is).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that we shouldn't do this manually, but I'm wondering why it was added automatically in some and not others? Was it because they were all not PRs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some of them were PRs.
Until
2022-10-26
, some PRs were not squashed when merged to themain
branch.If you squash merge, GitHub automatically adds a PR number to the commit message.
If you don't, then you get the original commit and the original commit message (so there will be no PR number).
You can notice, that the lines without PR numbers are always at the bottom of the lists, so we won't have such a problem in the future (unless someone forgets to squash when merging the PR).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to be more than formatting, so should be commented?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is 99.9% formatting: 50a627e
Moreover, this commit has been ignored for several years:
mamba/.git-blame-ignore-revs
Line 5 in d0c7458
(Don't look at the wrong commit message in
main
, but exactly this commit hash is already ignored inmain
).