fix(#1142): change DefaultAppSet from "fullsend" to "fullsend-ai"#1180
Conversation
The official GitHub Apps maintained by the fullsend-ai organization use the "fullsend-ai" prefix (fullsend-ai-fullsend, fullsend-ai-coder, etc.). Update the default so installs use the official apps without requiring an explicit --app-set flag. Orgs with existing "fullsend" app sets must now pass --app-set fullsend explicitly. Closes #1142 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Site previewPreview: https://51e5a664-site.fullsend-ai.workers.dev Commit: |
ReviewNo findings. Previous runReviewNo findings. Previous run (2)ReviewFindingsLow
Previous run (3)ReviewFindingsMedium
Low
Previous run (4)ReviewFindingsHigh
Medium
Low
|
TestInstallCmd_Flags and TestUninstallCmd_Flags still asserted the old "fullsend" default value for --app-set after the constant was changed to "fullsend-ai". Signed-off-by: Wayne Sun <gsun@redhat.com>
ralphbean
left a comment
There was a problem hiding this comment.
The [documentation-currency] finding is a good find; otherwise +1, thanks for this.
- Update installation.md flag tables and custom app sets section to
reflect the new "fullsend-ai" default
- Use "myorg" as the example prefix in --app-set help text since
"fullsend-ai" is now the actual default
- Fix TestAgentAppConfig_CustomAppSet to use a truly custom prefix
("my-custom") so it doesn't duplicate the default test
- Update stale comments in e2e cleanup to match new convention
Signed-off-by: Wayne Sun <gsun@redhat.com>
Review follow-upsCreated follow-up issues for actionable non-blocking review findings:
|
Update ADR 0033 slug examples and default value, fix cli-internals
diagram to show {appSet}-{role}, rewrite installation.md example to
use a non-default app-set, add migration note for existing users,
and clarify a misleading test case name.
Signed-off-by: Wayne Sun <gsun@redhat.com>
Keep the explicit flag to push users toward the fullsend-ai app set. Signed-off-by: Wayne Sun <gsun@redhat.com>
Signed-off-by: Wayne Sun <gsun@redhat.com>
Add step 8 to the planning phase of the code-implementation skill instructing the agent to search for old literal values when changing constants or defaults. When the task changes a constant from X to Y, the agent now searches for both the symbol name and the old value X as a string literal in test files, docs, and config. This addresses missed hardcoded assertions like those found in PR fullsend-ai#1180. Note: make lint could not run (Go toolchain permission denied in sandbox). Change is documentation-only (Markdown). Closes fullsend-ai#1221 Signed-off-by: fullsend-code <fullsend-code@users.noreply.github.com>
The official GitHub Apps maintained by the fullsend-ai organization use the "fullsend-ai" prefix (fullsend-ai-fullsend, fullsend-ai-coder, etc.). Update the default so installs use the official apps without requiring an explicit --app-set flag. Orgs with existing "fullsend" app sets must now pass --app-set fullsend explicitly.
Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com
Closes #1142
Post-script verification
fullsend/code/issue-1142)5f4e79e1610ae3ce8e8bcf95d530c1974ae6fcc1..HEAD)