Document, improve visibility, and adjust campaign discovery budget limits#11358
Merged
Document, improve visibility, and adjust campaign discovery budget limits#11358
Conversation
- Add comprehensive campaign-discovery-budgets.md documentation - Enhance discovery logging to show budget utilization - Add budget_exhausted and exhausted_reason fields to manifest - Include helpful warnings when budgets are exhausted with 0 items - Recompile security-alert-burndown campaign with updated discovery script Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Investigate noop status of campaign run and budget limits
Document and improve visibility of campaign discovery budget limits
Jan 22, 2026
Contributor
|
@copilot Suggest a more reasonable budget. |
- Increase max-discovery-items-per-run: 50 → 100 (default) - Increase max-discovery-pages-per-run: 3 → 5 (moderate) - This allows discovery to scan up to 500 items (5 pages × 100/page) - Still maintains conservative pacing with max-new-items-per-run: 3 - Balances thorough discovery with controlled rollout pace Co-authored-by: mnkiefer <8320933+mnkiefer@users.noreply.github.com>
Contributor
Author
Updated to moderate budget levels (commit 85813b1):
This scans up to 500 items (5 pages × 100/page) while keeping |
Copilot
AI
changed the title
Document and improve visibility of campaign discovery budget limits
Document, improve visibility, and adjust campaign discovery budget limits
Jan 22, 2026
mnkiefer
approved these changes
Jan 22, 2026
This was referenced Jan 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Campaign run #21255054636 was a no-op because discovery exhausted its budget (3 pages, 50 items max) without finding matching items. This is expected behavior for campaigns with conservative governance, but lacked visibility and documentation.
Changes
Documentation (
docs/campaign-discovery-budgets.md)Enhanced Discovery Logging (
actions/setup/js/campaign_discovery.cjs)Adjusted Campaign Budget (
.github/workflows/security-alert-burndown.campaign.md)max-discovery-items-per-runfrom 50 to 100 (default level)max-discovery-pages-per-runfrom 3 to 5 (moderate level)max-new-items-per-run: 3Impact: Campaign operators can now distinguish between true no-ops (no work available) and budget-limited runs (work may exist but wasn't discovered). The security-alert-burndown campaign now uses moderate budget levels that balance thorough discovery with controlled rollout pace.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.