Add python.instructions.md for Copilot code review#19202
Add python.instructions.md for Copilot code review#19202harupy merged 1 commit intomlflow:masterfrom
python.instructions.md for Copilot code review#19202Conversation
There was a problem hiding this comment.
Pull request overview
This PR adds GitHub Copilot code review instructions for Python files by creating a new instruction file that references existing Python style conventions.
- Creates
.github/instructions/python.instructions.mdwith frontmatter configuration to apply to all Python files - References the existing Python style guide at
dev/guides/python.md
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
python.instructions.md for Copilot code review
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Posted github/awesome-copilot#456 to check if this really works.
d72b250 to
199e8bc
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
199e8bc to
4f11490
Compare
Related Issues/PRs
N/A
What changes are proposed in this pull request?
Add
.github/instructions/python.instructions.mdto provide GitHub Copilot with Python code review guidelines. This file referencesdev/guides/python.mdfor style conventions.Reference: https://github.blog/ai-and-ml/unlocking-the-full-power-of-copilot-code-review-master-your-instructions-files/
How is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/build: Build and test infrastructure for MLflowHow should the PR be classified in the release notes? Choose one:
rn/none- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionShould this PR be included in the next patch release?
🤖 Generated with Claude Code