Repo Labeler Updated with label data action #25
Conversation
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
1 participant
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.
addresses #3
This PR introduces a new GitHub action that is ran whenever API_repo_labels/data/excel_labels_data.xlsx is updated. The action will run the script API_repo_labels/scripts/excel_to_json.py and prepare the JSON file needed to label repos.
If the action fails for any reason, it can also be run manually through GitHub actions.
A new logic is also introduced in API_repo_labels/scripts/repo_labeler.py to gracefully skip over labels with > 50 characters, which is GitHub's label limit. This was only an issue for the label: x- Infrastructure: Container Orchestration Platform, in which I changed its name in the JSON file to be x- Infrastructure: Container Orchestration