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

Check 3rd party repos before release or as regular CI job #782

Closed
mxmehl opened this issue Jun 22, 2023 · 1 comment · Fixed by #783
Closed

Check 3rd party repos before release or as regular CI job #782

mxmehl opened this issue Jun 22, 2023 · 1 comment · Fixed by #783
Assignees

Comments

@mxmehl
Copy link
Member

mxmehl commented Jun 22, 2023

At least as part of the release checklist, we should run the upcoming version of the linter against third-party repositories for which we know that they are

  • rather complex (like curl)
  • may use some "tricks" (dep5) (SAP repos come to mind)
  • are reliable REUSE adopters and keen to keep this status
  • are somewhat popular

This could be put into the checklist or as part of the regular checks in CI. There, we could pin these repos to specific commits to avoid false-negatives, but perhaps that's even not necessary as they run the linter themselves before adding commits.

@carmenbianca
Copy link
Member

Let's do this as CI job.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants