Repository navigation
Move gcp-vertex.env to common/env/ - #7
Conversation
Shared infrastructure env files belong under common/ to distinguish them from agent-specific env files. Update triage harness path. Signed-off-by: Claude <noreply@anthropic.com> Signed-off-by: Greg Allen <gallen@redhat.com>
PR Summary by QodoMove gcp-vertex env file to common/env and update triage harness path
AI Description
Diagram
High-Level Assessment
Files changed (2)
|
|
🤖 Finished Review · ✅ Success · Started 12:49 PM UTC · Completed 12:51 PM UTC |
|
Review skipped — this PR is already merged. The Posted by fullsend pre-review check |
|
🤖 Finished Retro · ✅ Success · Started 12:50 PM UTC · Completed 12:56 PM UTC |
|
Review skipped — this PR is already merged. The Posted by fullsend post-review check |
Retro: PR #7 — Move gcp-vertex.env to common/env/Workflow went well overall. This was a trivial human-authored refactoring PR (file rename + one-line path update) that was merged 20 seconds after creation. The review agent was dispatched via Timeline
Improvement opportunities (all already tracked)All candidate proposals are covered by existing open issues in
No new proposals needed — existing issues adequately cover the identified improvements. |
…ntegration - Sanitize JIRA_TOKEN before ::add-mask:: to prevent workflow-command injection via crafted tokens (finding fullsend-ai#1) - Remove reporter from required-field exemptions so validation catches projects that require Reporter without a default (finding fullsend-ai#4) - Track whether Labels is required and reject proposals with empty labels before create instead of letting Jira reject them (finding fullsend-ai#5) - Defer duplicate-check failure exit until after summary and Slack notification so already-created issues are reported (finding fullsend-ai#6) - Distinguish absent isLast from explicit false in createmeta pagination so a paginated response without total is not treated as single-page (finding fullsend-ai#7) - Document re-registering the agent source to the local Jira harness so fullsend resolves it instead of the remote pinned source (finding fullsend-ai#9) - Pass createmeta pages through temp files instead of --argjson to avoid argument-size limits on large projects; strip allowedValues (finding fullsend-ai#10) - Add _scribe_jira_api_with_status for error-body-preserving API calls and use it for label writes (finding fullsend-ai#11) - Regenerate bundled scripts Signed-off-by: anevans <anevans@redhat.com>
…ntegration - Sanitize JIRA_TOKEN before ::add-mask:: to prevent workflow-command injection via crafted tokens (finding fullsend-ai#1) - Remove reporter from required-field exemptions so validation catches projects that require Reporter without a default (finding fullsend-ai#4) - Track whether Labels is required and reject proposals with empty labels before create instead of letting Jira reject them (finding fullsend-ai#5) - Defer duplicate-check failure exit until after summary and Slack notification so already-created issues are reported (finding fullsend-ai#6) - Distinguish absent isLast from explicit false in createmeta pagination so a paginated response without total is not treated as single-page (finding fullsend-ai#7) - Document re-registering the agent source to the local Jira harness so fullsend resolves it instead of the remote pinned source (finding fullsend-ai#9) - Pass createmeta pages through temp files instead of --argjson to avoid argument-size limits on large projects; strip allowedValues (finding fullsend-ai#10) - Add _scribe_jira_api_with_status for error-body-preserving API calls and use it for label writes (finding fullsend-ai#11) - Regenerate bundled scripts Signed-off-by: anevans <anevans@redhat.com>
Summary
env/gcp-vertex.env→common/env/gcp-vertex.envhost_filespath to matchShared infrastructure env files (used by all agents) belong under
common/to distinguish them from agent-specific files likeenv/triage.env.Test plan
ggallen-sandbox/.fullsendconfig SHA and re-run/fs-triage🤖 Generated with Claude Code