-
Notifications
You must be signed in to change notification settings - Fork 50
[WIP] Fix mergeAt error by removing field filtering #2760
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.
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change | ||||||
|---|---|---|---|---|---|---|---|---|
|
|
@@ -61,7 +61,7 @@ steps: | |||||||
| gh search prs --repo ${{ github.repository }} \ | ||||||||
| --author "app/copilot" \ | ||||||||
| --created ">=$DATE_30_DAYS_AGO" \ | ||||||||
| --json number,title,state,createdAt,closedAt,mergedAt,author,body,labels,url,assignees,repository \ | ||||||||
| --json number,title,state,createdAt,closedAt,author,body,labels,url,assignees,repository \ | ||||||||
| --limit 1000 \ | ||||||||
| > /tmp/gh-aw/pr-data/copilot-prs.json | ||||||||
|
|
||||||||
|
|
@@ -116,17 +116,19 @@ For each PR in the dataset: | |||||||
| - Handle cases where body is null or empty | ||||||||
|
|
||||||||
| 2. **Categorize the PR outcome**: | ||||||||
| - **Merged**: `mergedAt` is not null | ||||||||
| - **Closed (not merged)**: `state` is "CLOSED" and `mergedAt` is null | ||||||||
| - **Note**: The `gh search prs` command doesn't return `mergedAt` in its JSON output | ||||||||
| - To determine merge status, you'll need to use `gh pr view <number> --json mergedAt` for each PR | ||||||||
|
||||||||
| - To determine merge status, you'll need to use `gh pr view <number> --json mergedAt` for each PR | |
| - To determine merge status, you'll need to use `gh pr view <number> --json mergedAt` for each PR | |
| - ⚠️ **Performance Note**: For large datasets (hundreds or thousands of PRs), checking merge status for each PR individually can be inefficient and may lead to GitHub API rate limiting. Consider batching requests, using the GitHub REST API to fetch multiple PRs at once, or limiting the number of PRs processed in a single run. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Corrected backtick usage: should use backticks around the command name for consistency with other code references in the document.