Skip to content

Rename PR review folder to .github-tracking #10931

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
brooke-hamilton wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Rename PR review folder to .github-tracking #10931

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
532618e
copilot tracking
brooke-hamilton Dec 11, 2025
6264af4
Merge branch 'main' into brooke-hamilton/github-tracking
brooke-hamilton Dec 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions .github/prompts/radius.code-review.prompt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,17 +11,17 @@ PR is an acronym for Pull Request.

You will create three files as part of this process: two markdown documents and one shell script. The first markdown document will detail the changes made in the PR on a file-by-file basis. The second markdown document will contain your review comments for each file and an overall assessment of the PR. The shell script will use the GitHub API to post your review comments from the second markdown file to the PR.

All files you create as part of this PR review will go into a folder named `pr-reviews` at the root of the project. If this folder does not exist, create it.
All files you create as part of this PR review will go into a folder named `.github-tracking` at the root of the project. If this folder does not exist, create it.

**Before Starting:**
Follow the "Before Starting a Review" section in `.github/instructions/code-review.instructions.md`, and additionally:
1. Create the `pr-reviews` folder if it does not exist.
1. Create the `.github-tracking` folder if it does not exist.

**Step 1: Analyze the Changes**
Follow the "Step 1: Analyze the Changes" section in `.github/instructions/code-review.instructions.md`.
For this pr, ${activePullRequest}, create a markdown document in the `pr-reviews` folder that describes in detail how each file has changed and what each file does, and what the changes are. Consider what the PR author wrote in the PR description as well as the changes that exist in each file.
For this pr, ${activePullRequest}, create a markdown document in the `.github-tracking` folder that describes in detail how each file has changed and what each file does, and what the changes are. Consider what the PR author wrote in the PR description as well as the changes that exist in each file.

Create `pr-reviews/pr-analysis-${prNumber}.md` with:
Create `.github-tracking/pr-analysis-${prNumber}.md` with:
- PR Summary section
- File-by-file analysis with:
- File purpose and role
Expand All @@ -31,7 +31,7 @@ Create `pr-reviews/pr-analysis-${prNumber}.md` with:
**Step 2: Provide Review Feedback**
Follow the "Step 2: Provide Review Feedback" section in `.github/instructions/code-review.instructions.md`, including all General Code Quality Criteria and Unit Test Review Criteria.

Create `pr-reviews/pr-review-${prNumber}.md` with:
Create `.github-tracking/pr-review-${prNumber}.md` with:
- Overall PR assessment
- Per-file review comments in this format:
path/to/file.ext
Expand Down
4 changes: 2 additions & 2 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,5 +81,5 @@ demo
# Helm debug output
.debug/

# Folder generated by the PR review Copilot prompt. See the .github/prompts folder.
pr-review/
# Folder for Copilot generated files
.github-tracking/
Loading