generated from kyma-project/template-repository
-
Notifications
You must be signed in to change notification settings - Fork 10
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
[rl-reuse_tool-4] Violation against OSS Rules of Play #22
Comments
This issue or PR has been automatically marked as stale due to the lack of recent activity. This bot triages issues and PRs according to the following rules:
You can:
If you think that I work incorrectly, kindly raise an issue with the problem. /lifecycle stale |
kyma-bot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Nov 9, 2023
dellagustin-sap
added a commit
to dellagustin-sap/infrastructure-manager
that referenced
this issue
Nov 9, 2023
The repository was not REUSE compliant becauce the name of the `.reuse` folder was incorrect. This was fixed by renaming it. Related issues: - kyma-project#22
dellagustin-sap
added a commit
to dellagustin-sap/infrastructure-manager
that referenced
this issue
Nov 9, 2023
The repository was not REUSE compliant becauce the name of the `.reuse` folder was incorrect. This was fixed by renaming it. Related issues: - kyma-project#22
kyma-bot
added a commit
that referenced
this issue
Nov 13, 2023
…-incorrect Fix #22 reuse folder has incorrect name
Disper
removed
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Nov 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A violation against the OSS Rules of Play has been detected.
Rule ID: rl-reuse_tool-4
Explanation: Is it compliant with REUSE rules? No
Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html
The text was updated successfully, but these errors were encountered: