Repository navigation
Add logIssue skill; migrate tech debt to GitHub Issues; add license - #23
Merged
Merged
Conversation
Moves tech-debt tracking from a markdown file requiring a full branch+PR cycle to GitHub Issues, filed via a new logIssue skill. Also adds licensing/citation metadata now that the repo is tagged as a forkable base, and fixes a test-isolation bug found during QA.
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.
Summary
logIssueskill (.claude/skills/log_issue.md) — files GitHub Issues directly viagh issue create, no branch/commit/PR required. For backlog items with no in-flight code change, as opposed to debt discovered mid-implementation on an active branch.docs/tech_debt.mditem to GitHub Issues (Remove setuptools<81 pin once OTel drops pkg_resources #18–Publish multi-arch (linux/amd64 + linux/arm64) images #22, labeledtech-debt) and deleted the file. UpdatedCLAUDE.md's Technical Debt reference anddocs/conf.py'sexclude_patternsto match — GitHub Issues is now the sole tech-debt tracking mechanism.LICENSE(BSD-3-Clause) and a matchingCITATION.cff(with ORCID), plus a License section in the README — now that the repo is tagged as a forkable base, it needs both.test_sysadmin_seeding_links_step_definition_to_user's cleanup deletedStepDefinitionandUserrows but never accounted forJobConfigurationrows referencing that user, causing an intermittent FK violation (fk_job_configurations_user_id) if any such row existed at cleanup time.CLI Verification
feature/log-issue-skillCITATION.cffvalidated as well-formed YAML-W, zero warnings), including aftertech_debt.md's deletion and theexclude_patternscleanupgh issue list --label tech-debt— confirmed all 5 issues (Remove setuptools<81 pin once OTel drops pkg_resources #18–Publish multi-arch (linux/amd64 + linux/arm64) images #22) filed and correctly labeleddocker compose exec api uv run pytest --cov=src --cov-fail-under=90 -q— 115 passed, 1 skipped, 98.25% coverage, after fixing the test-isolation bug found mid-rundocs/diagrams/infrastructure_topology.md— no service topology or data-flow changesApplication QA
logIssueexercised live, not just written — used to file all 5 tech-debt issues, confirmed correct titles, bodies, and labels on GitHubdiffpype-claude.readthedocs.io) confirmed live and current via direct fetch, ready to link from the repo's "About" section🤖 Generated with Claude Code