Introducing Rakuten Set Draft and Validation Workflow #473
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.
This PR introduces two significant additions to our project: a draft of the Rakuten set and a new GitHub Actions workflow designed to validate this set.
These changes aim at streamlining our validation processes with the Rakuten set. Below is a detailed overview of the contributions made through this PR:
New Additions:
rakuten-set-checks.yml
): A new GitHub Actions workflow has been introduced to automate the validation of the Rakuten set. This workflow is triggered on every push and pull request, ensuring that any changes to the Rakuten set are automatically validated against Google's predefined criteria. The well-known files check is disabled for now.Added [
.gitignore
].gitignore
]file for Python projects has been added to ensure that our repository remains clean by excluding unnecessary files generated during development and testing.