Standard license headers across repo#38732
Conversation
|
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
|
/azp help |
|
So that's why you wanted us to get to zero open PRs. ;) |
|
/azp list |
|
I think there are so many files you broke the bot. |
|
Kicked off the pipeline manually -> https://dev.azure.com/dnceng/public/_build/results?buildId=715585 |
|
|
db400d8 to
f6f8f05
Compare
|
I pushed my commit as a branch to dotnet/runtime and kicked it off manually with that: |
|
That'll probably work better. Both of the manual jobs I kicked off failed, probably because I didn't specify something correctly in the pipeline. |
0603b0c to
8fa45a9
Compare
8fa45a9 to
820c89e
Compare

We previously had a three-line license header on every file, except for files imported previously from mono, where we used a modified two-line license header on top of the one already there. The new guidance is to use a new two-line license header everywhere, such that we can have the same header regardless of whether the header originated in mono or not, and we can then enforce it via an editorconfig/analyzers/etc.
This PR automates the majority of the headers to be changed over.
This was done entirely with this (except for the addition to the .editorconfig file):
I will follow up subsequently to convert the stragglers, e.g. files with non-ASCII characters, VB, etc. I can also use the above to redo this at any time if we'd prefer to close this for now for whatever reason, e.g. concerns about conflicts, there's a better way to do it, etc.
cc: @richlander, @jkotas, @danmosemsft, @jeffschwMSFT