Repository navigation
feat(onboard): detect GitHub Issues as the tracker (#59, part C) - #125
Merged
Merged
Conversation
… the repository uses The survey gains an issue key row: the GitHub issue keys in branch names (issue-<n>, GH-<n>, <n>-words) and subjects (#<n>, GH-<n>), with the date guard kept, and the ticket pattern they imply as where.sh reads a GitHub tracker's branch. GH-<n> no longer names a Jira project. onboard's step 2 reads the repository's issues and merged pull requests when the history names no Jira project, proposes GitHub Issues, and asks which tracker holds the tickets when the history names a Jira project and GitHub holds issues too. Step 4 maps only the labels the issues carry to the roles, leaves a role with no fitting label to the issue's state, and proposes a ticket pattern only where the branches need one, asking where they are mixed; project.yaml is written as issue_tracker:, never jira:, with no location for the repository's own issues. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…es-onboard The pack's scenarios keep #116's filing scenarios and add the onboard ones; its test takes #116's WORK and DRAFT sets with ONBOARD beside them and the stub's get_label beside onboard's two searches. The ROADMAP's #59 row counts filing and onboard as landed, leaving the audit sweeps. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Another repository is proposed as the issues' location only when this one lists none and two references name it; references include the issue URL form; labels to map are checked against open issues carrying two; the workflow gate applies to the tracker chosen in the mixed case. The sandbox reset restores origin's branches from the bare remote and drops branches a setup made, so the onboard setups no longer break other packs. ISSUE_BRANCH ends a number at `_` too, as where.sh does. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
This is the last part of #59. Parts A (#113, #115), B (#116) and D (#124) have merged.
Closes #59
What it does
onboardnow recognises a repository whose tickets are GitHub issues. It lists the repository's issues and maps the labels to the workflow roles. Each recommendation carries the evidence for it: label counts, the references in pull request bodies, and the branch convention. The result is anissue_tracker:block withkind: github.docs/contracts.md, "The record", including the issue URL.workrefuses such an issue.issue keyrow coveringissue-<n>,GH-<n>and<n>-wordsbranch names and#<n>subjects. A number in a branch name now also ends at_, matchingwhere.sh.Also in this PR
The sandbox's
reset()now restoresorigin/*from the local bare remote and deletes local branches other than the pinned branch andmain, along with their config. Without this, the onboard setups brokePROJ-42-csv-loaderfor the other packs. A test covers a pin on a branch other thanmain.Review
Three adversarial rounds, and every finding is applied, with one exception: a schema check of
project.yamlthroughprofile.py, which would need new machinery. After main (#123, #124) was merged in,bash tests/checks.sh --allpassed all 12 steps, including the Python 3.9 run. When resolving the merge, ROADMAP's #59 row became a deferred row covering what is left: Projects fields, estimates and sub-issues.Origin: #59
Sandbox: Haiku.
tracker-gh-onboard10/10 on the branch and 0/10 on the current plugin;tracker-gh-onboard-mixed10/10 and 0/10.tracker-gh-onboard5/5.tracker-gh-onboard-mixed5/5 once the check was loosened. One run asked "Which tracker holds the project's tickets" as a heading with no?, and the old pattern missed it. With the new pattern all 10 baseline runs still fail.trigger-pr-createran onPROJ-42-csv-loaderafter the onboard pair, which confirms the reset fix.Canary: none
🤖 Generated with Claude Code