Repository navigation
archive projects with an archived flag on the note - #339
Merged
Merged
Conversation
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
1 participant
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.
A project can be archived from the project list menu, the overview page or its settings page by writing archived: true into the note's properties. Sub-projects inherit the flag. Archived projects leave the project list, pickers, folder and vault scopes, due reminders and the auto-archive sweep; an "Archived" toggle on the project list brings them back into view. The local API and MCP server get an archive endpoint and tool, and project listings include archived projects only on request.
Finished and abandoned projects had no way out of the list short of deleting them or moving them into an excluded folder, which also hid them from the API.
After merging, tag core/0.2.0 and api/0.2.0 so the packages publish; dotpm/cli#6 builds against @dotpm/api 0.2.0 and needs it on npm before its lockfile can be updated.