Add reuse badge in readme. - #48
Merged
Merged
Conversation
Add reuse badge in readme.
Member
|
@ajinkyapatil8190 does this need to go at the beginning of the file or can it appear anywhere? |
Member
Author
|
It can be anywhere in the file, but usually all badges are at the beginning of the readme so I kept it like that. |
axeluhl
approved these changes
Aug 26, 2026
axeluhl
left a comment
axeluhl
left a comment
Member
There was a problem hiding this comment.
LGTM. BTW, @ajinkyapatil8190 why would the tag as seen on https://github.com/ajinkyapatil8190/sailing-analytics/tree/patch-1 show "non-compliant?" How do we find out?
axeluhl
temporarily deployed
to
privileged-pr-build
August 27, 2026 08:45 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
axeluhl
added a commit
that referenced
this pull request
Aug 27, 2026
The 'code' filter used only negated rules under the default 'some' quantifier. picomatch treats '!README.md' as "any path except README.md", so a changed README.md still matched a rule and set code=true, forcing a full build for docs-only PRs (as seen on PR #48). Add a positive '**' rule and set predicate-quantifier: 'every' (the pinned v3.0.3 does not support the v4-only 'some-with-excludes'), so code is true only when a changed file matches the '**' rule AND all '!' exclusions, i.e. it is a non-trivial file. Assisted-By: Claude Opus 4.8
axeluhl
added a commit
that referenced
this pull request
Aug 27, 2026
The 'code' filter used only negated rules under the default 'some' quantifier. picomatch treats '!README.md' as "any path except README.md", so a changed README.md still matched a rule and set code=true, forcing a full build for docs-only PRs (as seen on PR #48). Add a positive '**' rule and set predicate-quantifier: 'every' (the pinned v3.0.3 does not support the v4-only 'some-with-excludes'), so code is true only when a changed file matches the '**' rule AND all '!' exclusions, i.e. it is a non-trivial file. Assisted-By: Claude Opus 4.8
axeluhl
temporarily deployed
to
privileged-pr-build
August 27, 2026 12:45 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
axeluhl
had a problem deploying
to
privileged-pr-build
August 28, 2026 16:35 — with
GitHub Actions
Error
GitHub Actions
Error
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add reuse badge in readme.
Issue Addressed by this PR
No Bug, just a chore for compliance.
Description
So, as per the OSPO guidelines, we have to make sure that the SAP open source repositories are all compliant - for this I created this PR to mark the compliance to the reuse rule.
Checklist for Pull Requests
bugXXXX