fix(tdd): replace non-standard @tdd_bug tags with @tdd_issue per CONTRIBUTING.md
CI / lint (push) Waiting to run
CI / typecheck (push) Waiting to run
CI / security (push) Waiting to run
CI / quality (push) Waiting to run
CI / unit_tests (push) Waiting to run
CI / integration_tests (push) Waiting to run
CI / e2e_tests (push) Waiting to run
CI / coverage (push) Blocked by required conditions
CI / benchmark-regression (push) Blocked by required conditions
CI / benchmark-publish (push) Waiting to run
CI / build (push) Waiting to run
CI / docker (push) Blocked by required conditions
CI / helm (push) Waiting to run
CI / status-check (push) Blocked by required conditions

Reviewed and APPROVED. Closes #2779.
This commit was merged in pull request #3292.
This commit is contained in:
2026-04-05 21:12:14 +00:00
committed by Forgejo
3 changed files with 3 additions and 3 deletions
+1 -1
View File
@@ -1,4 +1,4 @@
@tdd_bug @tdd_bug_797
@tdd_issue @tdd_issue_797
Feature: TDD Bug #797 — actor list should not cause a database update
Bug #797 reports that running ``agents actor list`` on a fresh checkout
@@ -1,4 +1,4 @@
@tdd_issue @tdd_issue_1080 @tdd_bug @tdd_bug_1080 @mock_only
@tdd_issue @tdd_issue_1080 @mock_only
Feature: TDD Bug #1080 — execution environment resolution ignores project-level override
As a developer
I want execution environment resolution to honour the 6-level precedence chain
@@ -1,4 +1,4 @@
@tdd_bug @tdd_bug_1076
@tdd_issue @tdd_issue_1076
Feature: TDD Bug #1076 — use_action() does not propagate automation_profile to Plan
As a developer
I want to verify that use_action() resolves the automation profile