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

[StyleCleanUp] Correct file header/license info (IDE0073) #10372

Open
wants to merge 21 commits into
base: main
Choose a base branch
from

Conversation

h3xds1nz
Copy link
Member

@h3xds1nz h3xds1nz commented Jan 30, 2025

Fixes #10371

Description

Puts the file header into correct state, most of the time its removal of the last line, some files didn't have the header at all (ref files).

Customer Impact

Everyone is informed the project is MIT.

Regression

No.

Testing

Local build.

Risk

None, no IL changes.

Microsoft Reviewers: Open in CodeFlow

@h3xds1nz h3xds1nz requested review from a team as code owners January 30, 2025 22:00
@dotnet-policy-service dotnet-policy-service bot added PR metadata: Label to tag PRs, to facilitate with triage Community Contribution A label for all community Contributions labels Jan 30, 2025
@robert-abeo
Copy link

Yikes, I would not do this

@ThomasGoulet73
Copy link
Contributor

ThomasGoulet73 commented Jan 31, 2025

@robert-abeo This isn't anything new, it has been done for multiple .Net projects (See dotnet/runtime#38793 and dotnet/winforms#9615). Personally I don't see anything wrong with it, it's low risk (Can compare the IL to see there isn't any functional changes), doesn't affect git blame (It's mostly just deleted lines) and shouldn't cause conflicts for existing PRs.

@h3xds1nz
Copy link
Member Author

I'll just add that anyone concerned with git blame runs with blame.ignoreRevsFile config or via param unless they're stuck in 1980.

@robert-abeo
Copy link

I wouldn't keep headers. If that's the convention here so be it (its a very old one I wouldn't keep).

If you are keeping the headers though I wouldn't remove this: // See the LICENSE file in the project root for more information.
Sometimes different components can have different licenses and the actual license file is the most important part. PLUS adding a project/license URL seems useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Community Contribution A label for all community Contributions PR metadata: Label to tag PRs, to facilitate with triage
Projects
None yet
Development

Successfully merging this pull request may close these issues.

IDE0073: Require file header
3 participants