Let's create a skill which ensures that any new code attribution which contains snippets of vendored code is properly attributed.
Ideally we have the following components
- A new check-code-attribution skill
A Skill which checks the PR diff agains the main branch for vendored / copied code, and if the attribution is missing, adds proper attribution.
- Integration to create-java-pr skill
The existing skill should check the attribution as well, allowing us to catch attribution issues quite early.
- Integration into CI
For any new PR targeting main, we should run the skill. See JS for some inspiration, on how skill invocation works:
https://github.com/getsentry/sentry-javascript/actions/runs/25426078130/workflow#L55-L77
TBD: should the CI check fail in case of error, how's the UX for resolving attribution issues
Let's create a skill which ensures that any new code attribution which contains snippets of vendored code is properly attributed.
Ideally we have the following components
A Skill which checks the PR diff agains the main branch for vendored / copied code, and if the attribution is missing, adds proper attribution.
The existing skill should check the attribution as well, allowing us to catch attribution issues quite early.
For any new PR targeting main, we should run the skill. See JS for some inspiration, on how skill invocation works:
https://github.com/getsentry/sentry-javascript/actions/runs/25426078130/workflow#L55-L77
TBD: should the CI check fail in case of error, how's the UX for resolving attribution issues