Skip to content

Polish the consumer-repo wording in the update-copyright skill #32

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

Open
alexander-yevsyukov wants to merge 1 commit into
base: master
Choose a base branch
from
+11 −9
Open

Polish the consumer-repo wording in the update-copyright skill #32

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
20 changes: 11 additions & 9 deletions skills/update-copyright/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ description: >
`config`, not by the consumer's copyright profile.
---

# Copyright Update
# Copyright update

**Command:** `python3 .agents/skills/update-copyright/scripts/update_copyright.py`

Expand Down Expand Up @@ -41,15 +41,17 @@ the automatic follow-up run after edits) and to repo-wide runs alike:
- The root files `gradle.properties`, `.codecov.yml`, and `lychee.toml`.
- `.github/workflows/<name>` when the `config` submodule carries a workflow of
the same basename in its `.github/workflows/` or `.github-workflows/`
directory. Repo-specific workflows — including `config:replaces` variants,
which use a different name — keep being stamped. When the submodule is not
directory. Repo-specific workflows — including variants that replace a
distributed workflow via a `config:replaces` directive and so ship under a
different basename — keep being stamped. When the submodule is not
checked out, the comparison is impossible and all workflow files are treated
as consumer-owned (stamped).

The `config` and `agents` source repositories declare no `config` submodule,
so the rule is inert there and their own `buildSrc/` etc. keep being stamped —
correct, since those files are project-owned at the source. Do **not** skip a
path merely because a same-named file exists somewhere under the `config/`
submodule: `config` carries files it does not distribute (e.g. its own
`README.md`). The set mirrors what `config`'s `migrate` script copies; if that
script changes what it distributes, update the script's exclusions to match.
so the rule is inert there and their own `buildSrc/`, `gradle.properties`, etc.
keep being stamped — correct, since those files are project-owned at the
source. Do **not** skip a path merely because a same-named file exists
somewhere under the `config/` submodule: `config` carries files it does not
distribute (e.g. its own `README.md`). The set mirrors what `config`'s
`migrate` script copies; if that script changes what it distributes, update
the exclusions in `update_copyright.py` to match.