Fix PR Labeler

[ok-coder1]

Fixed the python label being added to almost every PR for some reason.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[anmol098]

🤖 Code Review by Dume.ai, on behalf of @anmol098

Hello, this pull request has been reviewed by Dume.ai, the AI executive assistant to @anmol098.

Dume has carefully analyzed the changes and provided targeted inline comments to help improve clarity, quality, and maintainability of the code.

If you have any questions or need clarification, please refer to the inline feedback or feel free to tag @anmol098.

Review performed on 2025-06-09T04:49:56.972Z

—

Powered by Dume.ai – Your AI executive assistant for engineering workflows.

[anmol098]

💡 AI Review: - Code Quality: The change from "Pull Request Labeler" to Pull Request Labeler in the name field improves readability by removing unnecessary quotes.

• Code Quality: Adding name: Label PRs to the labeler job provides a clearer description of the job's purpose in the workflow run. This enhances readability and maintainability.
• Potential Issue: The workflow trigger is pull_request_target. Ensure this is the correct trigger for the intended use case. pull_request_target allows the workflow to access the contents of the base branch, but also introduces security considerations as it runs in the context of the base branch. If the workflow doesn't need to modify the base branch, consider using pull_request instead.

[anmol098]

💡 AI Review: - Bug and Issue Identification: The original python label configuration excluded sources/translation.json. The new configuration only includes sources/**.py, effectively dropping the exclusion. This might be unintentional, as changes to sources/translation.json might still require a translation label.

• Improvement Suggestion: The python section should be reviewed to ensure that it correctly identifies Python-related changes. Consider keeping the original configuration and adding .py to the glob, or explicitly adding a rule for translation.json if it should be labeled differently.
• Code Quality: The addition of .github/labeler.yml to the github_actions section is good for ensuring that changes to the labeler configuration itself are properly labeled.