Skip to content

Fix the template repo in the "Applying License Header to New Files" section. #146

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.

Sign up for GitHub

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

Merged
AkihiroSuda merged 1 commit into from
Jun 25, 2025
Merged

Fix the template repo in the "Applying License Header to New Files" section. #146

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,15 +81,15 @@ your chapter weird.

If you submit a contribution that adds a new file, please add the license
header. You can do so manually or use the `ltag` tool. The `ltag` templates
for filetypes are in the `containerd/project` repository but the files you want
for filetypes are in the `containerd/project-checks` repository but the files you want
to tag are most likely in the main containerd project or any of the possible
subprojects. You can pass the path to the project repo root to `ltag` but you
should run `ltag` in the directory where you have new files.


```console
$ go get github.com/kunalkushwaha/ltag
$ ltag -t {containerd/project rootdir}/script/validate/template
$ ltag -t {containerd/project-checks rootdir}/script/validate/template
```

The above will add the appropriate license header to Go language source files,
Expand Down