-
Notifications
You must be signed in to change notification settings - Fork 4
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
Integration of SPDX License Compliance Checker workflows #17
Conversation
* test 4 buggy files * *** AUTOMATED COMMIT | Applied Code Formatting and Cleanup ✨🍰✨*** * remove all files for testing --------- Co-authored-by: anirudTT <anirudTT@users.noreply.github.com>
* change this in this PR ; an already existing file * *** AUTOMATED COMMIT | Applied Code Formatting and Cleanup ✨🍰✨*** * try with a 2024 year * try this workflow * try with a better comment approach * update comment * update workflow name * lets update lc checker and try * test failure * *** AUTOMATED COMMIT | Applied Code Formatting and Cleanup ✨🍰✨*** * test without weird ''' block within the code * update name * update comment again * correct spelling * correct file name as well * add thank you in the end * keep it a same as main * remove this file for starting PR * make simar to main * *** AUTOMATED COMMIT | Applied Code Formatting and Cleanup ✨🍰✨*** * re update comment * update name again --------- Co-authored-by: anirudTT <anirudTT@users.noreply.github.com>
to reflect the correct copyright notice. Co-authored-by: Milan Kordic <78221808+milank94@users.noreply.github.com>
to reflect the correct copyright notice. Co-authored-by: Milan Kordic <78221808+milank94@users.noreply.github.com>
* add dynamic year * introduce bugs to test * *** AUTOMATED COMMIT | Applied Code Formatting and Cleanup ✨🍰✨*** * try again * *** AUTOMATED COMMIT | Applied Code Formatting and Cleanup ✨🍰✨*** * add a comment * rename files * *** AUTOMATED COMMIT | Applied Code Formatting and Cleanup ✨🍰✨*** * set as env variable to ensure PR is commented * correct comment structuring * add a lc header here * check that it does work * check if this errors out * remove this and check * *** AUTOMATED COMMIT | Applied Code Formatting and Cleanup ✨🍰✨*** * add in all correct stuff n check * re do the workflow * *** AUTOMATED COMMIT | Applied Code Formatting and Cleanup ✨🍰✨*** * add more check and verify * *** AUTOMATED COMMIT | Applied Code Formatting and Cleanup ✨🍰✨*** * make it more easier to understand errors * check now that no errors come * try this * try this checker * try with rename * check this Ai stuff * correct and check * update all to allow for broader mentions * correct mention * delete this tester file --------- Co-authored-by: anirudTT <anirudTT@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
made requested changes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated:
- the workflow name as I felt both almost are named the same
- updated to remove the name python files from PR comment body
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice! Looks good
Integration of SPDX License Compliance Checker workflows-- within Github Actions
Overview
This pull request introduces changes to GitHub Actions workflows, focusing on ensuring adherence to SPDX license requirements for Python files. It adds two new workflows,
check-license-year.yml
andlicense-checker.yml
, to automate the verification of SPDX license headers and the checking of the correct license year within all changed and new Python files involved/added via a PR tomain
.Additions / Changes to repository via PR or otherwise :
SPDX License Year Validation Workflow (
check-license-year.yml
):SPDX License Header Check Workflow (
license-checker.yml
):check_copyright_config.yaml
.Configuration File (
check_copyright_config.yaml
):Updates to CONTRIBUTING.md:: to better explain contributors on how to navigate workflow failures and passing criteria.
Outside the PR: https://github.com/tenstorrent/benchmarking/settings/rules --- rule set will be added to prevent a PR being merged unless all checks are passed
How It Works
Upon opening or updating a PR, the newly implemented workflows run automatically. Non-compliance with our SPDX licensing standards triggers informative comments within the PR, illustrating precisely what needs to be corrected. (See included screenshots for examples of these automated comments.)
Screenshots
PR comments:
Shows clearly that the workflow failed: