Create GH action for code formatting

[anandhu-eng]

✅ PR Checklist

• Target branch is dev

📌 Note: PRs must be raised against dev. Do not commit directly to main.

✅ Testing & CI

• Have tested the changes in my local environment, else have properly conveyed in the PR description
• The change includes a GitHub Action to test the script(if it is possible to be added).
• No existing GitHub Actions are failing because of this change.

📚 Documentation

• README or help docs are updated for new features or changes.
• CLI help messages are meaningful and complete.

📁 File Hygiene & Output Handling

• No unintended files (e.g., logs, cache, temp files, pycache, output folders) are committed.

🛡️ Safety & Security

• No secrets or credentials are committed.
• Paths, shell commands, and environment handling are safe and portable.

🙌 Contribution Hygiene

• PR title and description are concise and clearly state the purpose of the change.
• Related issues (if any) are properly referenced using Fixes # or Closes #.
• All reviewer feedback has been addressed.

[github-actions]

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

[github-actions]

🤖 AI PR Review Summary\n\nAdds a GitHub Actions workflow to automatically format Python files on every push, excluding commits made by the automation bot itself. The workflow installs autopep8, formats modified Python files, and commits any changes back to the repository. Risks include potential conflicts or unintended formatting changes that may disrupt ongoing work. The design relies on a GitHub App token for authentication and uses a simple diff-based file filter, which may miss edge cases such as renamed or deleted files.

[github-actions]

🤖 AI PR Review Summary\n\nThis PR updates the CLA workflow to expand the allowlist for automated users and introduces a new GitHub Actions workflow for automatic Python code formatting using autopep8. The formatting workflow runs on all branches except when triggered by the mlc-automations user, installs dependencies, formats changed Python files, and commits any changes back to the repo. Risks include potential unintended commits if formatting changes are applied unexpectedly and possible permission issues with the GitHub token. The design is straightforward but could benefit from additional safeguards and clearer filtering of files to format.

[github-actions]

🤖 AI PR Review Summary\n\nThis PR adds an allowlist entry for 'mlc-automations' in the CLA check workflow and introduces a new GitHub Actions workflow for automatic Python code formatting using autopep8. The formatting workflow runs on all branches except when triggered by the 'mlc-automations' actor to avoid recursion. It checks for modified Python files, formats them, and commits the changes automatically. Risks include potential unintended commits if the formatting changes are not desired, and the use of git commands in the workflow requires careful permission handling. The design is straightforward but could benefit from additional safeguards such as limiting the scope of files or adding a dry-run mode.

[github-actions]

🤖 AI PR Review Summary\n\nThis PR introduces a new GitHub workflow for automatic Python code formatting using autopep8, and updates the CLA workflow to extend the allowlist. The main code changes in mlc/action.py focus on code cleanup, formatting improvements, and minor refactoring without changing core logic. Risks are low as no functional changes are introduced, but the new formatting workflow could cause unexpected formatting commits if not properly tested. Design-wise, the formatting workflow is gated to exclude the automation bot itself to avoid infinite loops, which is a good practice.

[github-actions]

🤖 AI PR Review Summary\n\nThis PR adds a new GitHub workflow for automatic Python code formatting using autopep8 and updates the CLA workflow to include an additional user in the allowlist. It also refactors the Action class in mlc/action.py for improved readability and consistency, including better logging, formatting, and minor code style improvements. The risks are low as the changes are mostly additive and stylistic, but the new formatting workflow could cause unexpected commits if autopep8 modifies files unexpectedly. The design is straightforward, but the formatting workflow assumes the presence of Python files and may need further testing to ensure it does not interfere with other workflows.

[github-actions]

🤖 AI PR Review Summary\n\nThis PR adds a new GitHub workflow for automatic Python code formatting using autopep8 and updates the CLA workflow to include an additional user in the allowlist. The main code changes in mlc/action.py improve code formatting, add comments, and refactor some logic for clarity and consistency. The risks are low as the formatting workflow runs conditionally and the code changes are mostly stylistic and minor refactors. However, the new formatting workflow commits directly to branches which could cause unexpected pushes if not carefully monitored. There are no major design issues, but some minor improvements in logging and error handling could be considered.

[github-actions]

🤖 AI PR Review Summary\n\nThis PR introduces a new GitHub workflow for automatic Python code formatting using autopep8, updates the CLA workflow to include an additional allowlist user, and performs a version bump to 1.2.0. The main code changes in mlc/action.py include code style improvements, enhanced logging, and minor refactoring for readability and consistency. Risks include potential issues with the new formatting workflow committing changes automatically, which might conflict with ongoing PRs or cause unexpected commits. The Action class changes appear low risk but should be tested for backward compatibility and correct behavior in repo loading and item management.