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

Update copyright year and copyright string #1432

Merged
merged 2 commits into from
Jan 31, 2024

Conversation

Aaron-Junker
Copy link
Contributor

Description

Updates copyright year in tests and changed copyright string to match other Microsoft products (example: https://github.com/microsoft/PowerToys/pull/30689/files)

Motivation and Context

New year and similarity with other Microsoft Products

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

@marcelwgn
Copy link
Collaborator

Thank's for creating this PR! Out of curiosity, is there a reason you only changed those with the year being 2023? :)

@Aaron-Junker
Copy link
Contributor Author

Thank's for creating this PR! Out of curiosity, is there a reason you only changed those with the year being 2023? :)

No. I just missed them. I fixed this now.

@karkarl karkarl merged commit d943082 into microsoft:main Jan 31, 2024
2 checks passed
karkarl pushed a commit that referenced this pull request Jul 15, 2024
<!--- Provide a general summary of your changes in the Title above -->

## Description

Updates copyright year in tests and changed copyright string to match
other Microsoft products (example:
https://github.com/microsoft/PowerToys/pull/30689/files)

## Motivation and Context

New year and similarity with other Microsoft Products

## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran
to -->
<!--- see how your change affects other areas of the code, etc. -->

## Screenshots (if appropriate):

## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)
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.

None yet

3 participants