microsoft / microsoft/finops-toolkit

GitHub action to add copyright headers

Open
#216 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Help wanted ✨ Skill: DevOps Tool: PowerShell
Dominant language
PowerShell
Stars
603
Forks
249
Avg merge
7d 11h
Merged PRs (30d)
11

Description

⚠️ Problem

Copyright headers are required, but easily forgotten.

🛠️ Solution

Create a GitHub action that runs the Add-CopyrightHeaders script for every PR.
If any files are updated, commit and push to the branch.
If any new file types are discovered, block the PR and leave a comment to add the comment characters or exclude the file type.
Re-run the check with each commit.

ℹ️ Additional context

Details about updating the script are documented at src/scripts/README.md.

🙋‍♀️ Ask for the community

We could use your help:

  1. Please vote this issue up (👍) to prioritize it.
  2. Leave comments to help us solidify the vision.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Add-CopyrightHeaders script and the guidance in src/scripts/README.md, then review the repository's existing GitHub Actions workflows. The work is done when the action runs on each commit, updates and pushes headers when needed, and blocks and comments on unsupported file types as described.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, powershell
Domain
ci-cd, devops, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.