Repository navigation
feat: relai tidy and post-merge hook; discovery follow-ups; test minors - #11
Merged
Merged
Conversation
…overy follow-ups (depth, links in find, config evidence); duplicate provides key keeps both lists Closes relai-fwx
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
Housekeeping after merges should not depend on someone remembering it: on 2026-11-04 about thirty tasks stayed "in progress" after their code was merged. This PR makes it automatic, fixes the minors of the independent light test, and does the first follow-ups of the discovery.
relai tidy [--apply](OpenSpecauto-tidy-and-discovery-followups): closes a task when a commit on the default branch says so with a keyword and the id (Closes relai-7nk,fixes #relai-7nk); refreshes.beads/issues.jsonlwithout the owner e-mail; deletes fully merged local branches (git branch -d). Dry run by default, never commits, closes nothing from a feature branch, and leaves a task that is only named open (it is reported). Ids are matched whole (p-1is notp-10).relai init --hooksnow also installs apost-mergehook runningrelai tidy --applyafter every pull or merge. Thepre-commithook givesbdat most 20 s (RELAI_HOOK_TIMEOUT), with or withouttimeout(1)(test minor Golden-path scaffolding: relai new <template> <dir> #2).provides:key kept only the last list and lost the first silently; both are kept and a warning is printed (test minor Cross-repo index, degraded-mode handoff, release pipeline #1).--depth Nfordiscover --linksandindex build --scan(nested repos named by path, node_modules/vendor/build skipped, never inside a repo);relai findshowsworks with:and puts the repos linked with the one you are in first ([linked from here]);--proposenow also proposes a repo named in two or more CI/deploy/config files (workflows, k8s, compose, yaml...) because that is far more often a real dependency than a name in a document, and--min-weak Nsets the document-only threshold (default 5).AGENTS.mdand the README tell contributors to end the commit message of finished work withCloses <task id>.Verified
go vet,go test -race -count=1 ./...(96 tests); tidy on a synthetic repo (only keyword+id closes,p-10untouched, already-closed ignored, feature branch closes nothing, only merged branches deleted, owner removed from the export, no commit, no bd = tasks left open and said so); hooks tested with a hangingbd, a failingrelai, and withouttimeout(1).Not done / for review
--promptyet. Both are in the next test session.Closeslines, so tidy will not close it; those tasks are closed by hand once.v0.3.0exists but GitHub did not start the release workflow (a GitHub incident was open at the time); see the conversation.Closes relai-fwx