Fill in the developer documentation gaps #514
No reviewers
Labels
No labels
blocked
duplicate
needs
approval
needs
criteria
needs
estimate
needs
tests
question
step
doing
step
review
step
testing
step
todo
step
uat
type
admin
type
alert
type
bug
type
change
type
defect
type
epic
type
idea
type
incident
type
investigation
type
spike
type
story
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
External/card-drop!514
Loading…
Reference in a new issue
No description provided.
Delete branch "cursor/487-developer-docs"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up 2 of 3 from #487, split out as you asked on the issue. Documentation only, no code changes.
This covers all three items in the Documentation gaps section of the checklist.
README gets a Development section with the three CI commands in the order the workflows run them, the migration workflow (
db:create->build->db:up, and why the build has to come first: the migrations run againstdist/), where environment variables live, and whatPOST /api/reload-dbis for.New
docs/development.mdfor the "how do I add a command" question. Everything is registered insrc/registry.tsand nothing is auto-discovered, which is the bit worth writing down. It covers the id-then-instance registration signature, theEnvironmentfilter being applied at registration rather than dispatch, that buttons and dropdowns are routed on the first space-separated segment of the custom id, and the test conventions intests/.Cross-links in the three existing docs. Each of
cards.md,google-drive-sync.mdandlogger.mdnow points at where its environment variables live and says what tests are expected when that area changes, plus links between themselves and the README.Two small README bugs fixed while I was in there:
yarn Install->yarn install. The capital I fails on a case-sensitive shell.cp .env.template .env->cp .env.example .env. There is no.env.templatein the repo, so following the README as written left you without a config file.Two things I chose to be explicit about rather than paper over. The dispatchers on this branch do not
awaitexecute, sodocs/development.mdsays so and tells contributors to catch their own failures until #512 lands. Likewise the README says/api/reload-dbis currently unauthenticated and points at #512 for the token. Both notes will need a trim once #512 merges - happy to do that as part of merging it, or leave them as accurate history.yarn lintstill passes. No overlap with #512 or #513: #512 addsdocs/webhooks.mdbut touches neither the README nor these three docs.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.