UAT: Systematic missing milestone assignments on open PRs — 12 of 20 open PRs have no milestone #3895

New issue

Open

opened 2026-04-06 07:16:08 +00:00 by freemo · 0 comments

freemo commented

2026-04-06 07:16:08 +00:00

Owner

Summary

CONTRIBUTING.md §"Pull Request Process" item 11 states:

Assign a milestone. Every PR must be assigned to the same milestone as its linked issue(s). If the linked issues span multiple milestones, assign the PR to the milestone of the primary issue. A PR without a milestone will not be reviewed.

A review of the 20 most recent open PRs reveals that 12 of 20 (60%) have no milestone assigned, in direct violation of this requirement.

Evidence

PRs missing milestone (12/20)

PR	Title	Milestone
#3880	`fix(validation): replace positional key=value args with --key value named options`	❌ NONE
#3788	`docs: session 2026-04-06 documentation updates`	❌ NONE
#3774	`fix: Update for Click 8.2+ compatibility and fix quality gates`	❌ NONE
#3712	`docs(timeline): update schedule adherence Day 95 final`	❌ NONE
#3696	`docs: document v3.8.1 changes — skeleton context inheritance, actor YAML-first path, checkpoint triggers`	❌ NONE
#3554	`chore(agents): fix ca-architecture-guard — add hostname resolution guidance`	❌ NONE
#3551	`chore(agents): fix ca-test-infra-improver — reduce health comment spam`	❌ NONE
#3480	`chore(agents): fix ca-architecture-guard clone failure and self-issue-filing`	❌ NONE
#3478	`chore(agents): fix ca-test-infra-improver health comment spam`	❌ NONE
#3458	`fix(cli): add missing Origin panel, Overridden field, Winner indicator, and JSON envelope in config get output`	❌ NONE
#3456	`fix(tui): make /help command list all catalogued slash commands from SLASH_COMMAND_SPECS`	❌ NONE
#3455	`fix(cli): add <REGEX> positional argument to agents plan list command`	❌ NONE
#3454	`fix(providers): export dedicated LLM provider classes from providers/llm/__init__.py`	❌ NONE
#3393	`docs: update CHANGELOG and reference docs for session 3377`	❌ NONE

PRs with milestone (8/20)

PR	Title	Milestone
#3846	`fix(resource): add overlay to ResourceTypeConfigSchema._VALID_STRATEGIES`	✅ v3.6.0
#3837	`fix(cli): change agents validation attach extra args to --key value format`	✅ v3.7.0
#3473	`fix(cli): implement real actor execution and spec-required output panels in agents session tell`	✅ v3.5.0
#3466	`fix(config): remove undocumented LOCAL scope from ConfigLevel/ConfigScope enums`	✅ v3.7.0
#3416	`chore(agents): add mandatory label requirements to supervisor issue creation`	✅ v3.6.0
#3390	`docs(spec): document MCP 1.4.0 error extraction from content[0].text in MCPToolAdapter`	✅ v3.7.0

Root Cause Analysis

The pattern suggests that automated agents creating PRs (ca-issue-worker, product-builder, etc.) are not consistently assigning milestones when creating pull requests. The PRs without milestones include:

Documentation PRs (timeline updates, changelog updates) — these appear to be created without milestone assignment as they are considered "housekeeping"
Agent improvement PRs (ca-architecture-guard, ca-test-infra-improver fixes) — these lack milestone assignment
Bug fix PRs (#3458, #3456, #3455, #3454) — these are substantive bug fixes that should be assigned to the milestone of their linked issues

Expected Behavior (per CONTRIBUTING.md)

Every open PR must have a milestone assigned. The milestone should match the milestone of the linked issue(s).

For example:

PR #3458 fixes agents config get output — its linked issue should have a milestone, and the PR should inherit it.
PR #3774 fixes Click 8.2+ compatibility — this is a bug fix that should be assigned to the current active milestone.

Impact

Review blocking: Per CONTRIBUTING.md, "A PR without a milestone will not be reviewed." These 12 PRs are technically blocked from review.
Release planning: Without milestone assignments, it is impossible to track which PRs are targeted for which release.
Process compliance: 60% non-compliance rate indicates a systematic tooling or process gap.

Recommended Fix

Assign milestones to all 12 non-compliant open PRs listed above.
Update automated agents (ca-issue-worker, product-builder) to always assign the milestone from the linked issue when creating PRs.
Consider adding a CI check or Forgejo webhook that blocks PR submission without a milestone.

Automated by CleverAgents Bot
Supervisor: UAT Testing | Agent: ca-uat-tester

## Summary CONTRIBUTING.md §"Pull Request Process" item 11 states: > **Assign a milestone.** Every PR must be assigned to the same milestone as its linked issue(s). If the linked issues span multiple milestones, assign the PR to the milestone of the primary issue. **A PR without a milestone will not be reviewed.** A review of the 20 most recent open PRs reveals that **12 of 20 (60%) have no milestone assigned**, in direct violation of this requirement. --- ## Evidence ### PRs missing milestone (12/20) | PR | Title | Milestone | |----|-------|-----------| | #3880 | `fix(validation): replace positional key=value args with --key value named options` | ❌ NONE | | #3788 | `docs: session 2026-04-06 documentation updates` | ❌ NONE | | #3774 | `fix: Update for Click 8.2+ compatibility and fix quality gates` | ❌ NONE | | #3712 | `docs(timeline): update schedule adherence Day 95 final` | ❌ NONE | | #3696 | `docs: document v3.8.1 changes — skeleton context inheritance, actor YAML-first path, checkpoint triggers` | ❌ NONE | | #3554 | `chore(agents): fix ca-architecture-guard — add hostname resolution guidance` | ❌ NONE | | #3551 | `chore(agents): fix ca-test-infra-improver — reduce health comment spam` | ❌ NONE | | #3480 | `chore(agents): fix ca-architecture-guard clone failure and self-issue-filing` | ❌ NONE | | #3478 | `chore(agents): fix ca-test-infra-improver health comment spam` | ❌ NONE | | #3458 | `fix(cli): add missing Origin panel, Overridden field, Winner indicator, and JSON envelope in config get output` | ❌ NONE | | #3456 | `fix(tui): make /help command list all catalogued slash commands from SLASH_COMMAND_SPECS` | ❌ NONE | | #3455 | `fix(cli): add <REGEX> positional argument to agents plan list command` | ❌ NONE | | #3454 | `fix(providers): export dedicated LLM provider classes from providers/llm/__init__.py` | ❌ NONE | | #3393 | `docs: update CHANGELOG and reference docs for session 3377` | ❌ NONE | ### PRs with milestone (8/20) | PR | Title | Milestone | |----|-------|-----------| | #3846 | `fix(resource): add overlay to ResourceTypeConfigSchema._VALID_STRATEGIES` | ✅ v3.6.0 | | #3837 | `fix(cli): change agents validation attach extra args to --key value format` | ✅ v3.7.0 | | #3473 | `fix(cli): implement real actor execution and spec-required output panels in agents session tell` | ✅ v3.5.0 | | #3466 | `fix(config): remove undocumented LOCAL scope from ConfigLevel/ConfigScope enums` | ✅ v3.7.0 | | #3416 | `chore(agents): add mandatory label requirements to supervisor issue creation` | ✅ v3.6.0 | | #3390 | `docs(spec): document MCP 1.4.0 error extraction from content[0].text in MCPToolAdapter` | ✅ v3.7.0 | --- ## Root Cause Analysis The pattern suggests that automated agents creating PRs (ca-issue-worker, product-builder, etc.) are not consistently assigning milestones when creating pull requests. The PRs without milestones include: 1. **Documentation PRs** (timeline updates, changelog updates) — these appear to be created without milestone assignment as they are considered "housekeeping" 2. **Agent improvement PRs** (ca-architecture-guard, ca-test-infra-improver fixes) — these lack milestone assignment 3. **Bug fix PRs** (#3458, #3456, #3455, #3454) — these are substantive bug fixes that should be assigned to the milestone of their linked issues --- ## Expected Behavior (per CONTRIBUTING.md) Every open PR must have a milestone assigned. The milestone should match the milestone of the linked issue(s). For example: - PR #3458 fixes `agents config get` output — its linked issue should have a milestone, and the PR should inherit it. - PR #3774 fixes Click 8.2+ compatibility — this is a bug fix that should be assigned to the current active milestone. --- ## Impact - **Review blocking**: Per CONTRIBUTING.md, "A PR without a milestone will not be reviewed." These 12 PRs are technically blocked from review. - **Release planning**: Without milestone assignments, it is impossible to track which PRs are targeted for which release. - **Process compliance**: 60% non-compliance rate indicates a systematic tooling or process gap. --- ## Recommended Fix 1. Assign milestones to all 12 non-compliant open PRs listed above. 2. Update automated agents (ca-issue-worker, product-builder) to always assign the milestone from the linked issue when creating PRs. 3. Consider adding a CI check or Forgejo webhook that blocks PR submission without a milestone. --- **Automated by CleverAgents Bot** Supervisor: UAT Testing | Agent: ca-uat-tester

freemo referenced this issue

2026-04-06 07:17:05 +00:00

[Automated] CleverAgents Build Session - 2026-04-06 #3775

freemo referenced this issue

2026-04-06 07:21:26 +00:00

[Automated] CleverAgents Build Session - 2026-04-06 #3775

freemo referenced this issue

2026-04-06 10:35:53 +00:00

[Automated] CleverAgents Build Session - 2026-04-06 #3775