Repository navigation
Conversation
Contributor
There was a problem hiding this comment.
🟢 Approved
No active review issues block the addition of the basecamp projects recent command.
No open issues 🎉
What changed in this PR
Adds basecamp projects recent using the existing SDK to show the current user’s recently visited projects in API visit order, separate from the full project listing.
Changes:
- Adds the command with help describing its single-page result and 50-visit limit.
- Registers it in the command catalog, CLI surface snapshot, and API coverage documentation.
- Adds four unit tests and a read-only smoke test.
[!TIP]
If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or rungh pr ready --undo.
Click "Ready for review" or rungh pr readyto reengage.
| File | Description |
|---|---|
internal/commands/projects.go |
Implements and registers projects recent using Projects().ListRecent. |
internal/commands/projects_recent_test.go |
Tests request routing, visit order, empty results, API refusal, and argument rejection. |
internal/commands/commands.go |
Adds recent to the project command catalog. |
e2e/smoke/smoke_projects.bats |
Adds a read-only smoke check for the response structure. |
API-COVERAGE.md |
Documents the endpoint, ordering, and result limits. |
.surface |
Records the command and inherited flags for both project aliases. |
Review effort: Balanced
Contributor
There was a problem hiding this comment.
All reported issues were addressed across 6 files
Tip: Get a Slack DM when cubic finishes reviewing your PRs. Connect Slack
View guided diff | Turn on auto-fix | Re-trigger cubic
Copilot
AI
dismissed their stale review, a newer Copilot review was requested
November 8, 2026 18:44
This branch has not been deployed
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.

What
Adds
basecamp projects recentto list the current user's recently visited projects through the supported SDKProjects().ListRecentcall. Preserves the API's visit order; this is not a sorted or paginated replacement forprojects list.Updates command help, the command catalog, the surface snapshot, API coverage documentation, and a read-only smoke case. Includes the standard missing-app-context error and a
projects show <id>next-step hint, preserving the selected profile/account and addressing the scoped review suggestions.Why
The API and SDK already expose recent projects, but the CLI has no command for this personal project list.
Testing
bin/ci(make check) passes on final committed head4349999e1a8045bc9f3ec954baacdba2625f7f9d, usingmise exec golangci-lint@2.11.1 ruby@3.4.12 -- bin/ci.TestProjectsRecenttests rerun on that exact committed head: exact GET and visit order, empty result, API refusal, argument rejection before a request, missing app context, the show hint, and preservation of the selected profile/account in that hint.The real development response contained one project. Multi-project ordering is unit-tested, not demonstrated live. The API's 50-visit cap and access filtering were not separately boundary-tested. No expanded permission matrix, Windows, ONCE, production/beta, release or deployment validation is claimed. Own development token was revoked and the server stopped after verification.