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

Apply and enforce file-level license headers #440

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

lieut-data
Copy link
Member

Summary

Use mattermost-govet to ensure each file begins with the appropriate header, then fix all instances for built source code.

// Copyright (c) 2019-present Mattermost, Inc. All Rights Reserved.
// See LICENSE.txt for license information.

Note that this renames LICENSE to LICENSE.txt purely to align on the copyright messaging across repos.

Ticket Link

None

@lieut-data lieut-data force-pushed the updated-license-header branch from 6b1a3ad to 763da60 Compare January 23, 2025 19:47
Use `mattermost-govet` to ensure each file begins with the appropriate header, then fix all instances for built source code.

```
// Copyright (c) 2019-present Mattermost, Inc. All Rights Reserved.
// See LICENSE.txt for license information.
```

Note that this renames `LICENSE` to `LICENSE.txt` purely to align on the
copyright messaging across repos.
@lieut-data lieut-data force-pushed the updated-license-header branch from 763da60 to 6c72240 Compare January 23, 2025 21:38
@lieut-data lieut-data marked this pull request as ready for review January 24, 2025 17:23
@lieut-data lieut-data requested a review from wiggin77 as a code owner January 24, 2025 17:23
@lieut-data lieut-data force-pushed the updated-license-header branch from f573fb9 to f13d253 Compare January 27, 2025 18:49
@wiggin77
Copy link
Member

@lieut-data a bunch of files ended up with duplicated copyright notices with different dates. I commented on the first few I found, but didn't comment on the rest. Is the tool meant to detect existing copyright messages and update or replace them?

@lieut-data
Copy link
Member Author

Thanks for your careful eye, @wiggin77! I thought I had pruned the cases where this had occurred early on, but I clearly wasn't rigorous enough. I've gone through all the pre-packaged plugins again to check for duplicate Copyrights and fixed the ones here as well as in the Jira PR. (I've also surfaced some weird files in Boards I'm looking into separately.)

@lieut-data lieut-data requested a review from wiggin77 January 30, 2025 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants