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

Add guidance on adding copyright and license header to new source files #6140

Merged
merged 1 commit into from
Feb 9, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions .github/CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -149,6 +149,25 @@ Additional references:
While not required, we appreciate any contributors who add this label and create the issue themselves.
Even better, all contributors are free to contribute the documentation themselves.
(See [Contributing to documentation related to PowerShell](#contributing-to-documentation-related-to-powershell) for more info.)
* If your change adds a new source file, ensure the appropriate copyright and license headers is on top.
It is standard practice to have both a copyright and license notice for each source file.
* For `.h`, `.cpp`, and `.cs` files use:

// Copyright (c) Microsoft Corporation. All rights reserved.
// Licensed under the MIT License.

* For `.ps1` and `.psm1` files use:

# Copyright (c) Microsoft Corporation. All rights reserved.
# Licensed under the MIT License.

* If your change adds a new module manifest (.psd1 file), ensure that:

```powershell
Author = "PowerShell"
Company = "Microsoft Corporation"
Copyright = "Copyright (c) Microsoft Corporation. All rights reserved."
```

### Pull Request - Work in Progress

Expand Down