Repository navigation
feat(need-fix-to-issue): categorize and deduplicate generated issues - #611
Merged
Merged
Conversation
Contributor
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
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.
Closes #292.
Adds a
need-fix-to-issuecomposite action that creates TODO/FIXME issues, assigns the organization'sBugtype to untyped issues, and closes duplicates. The reusable workflow performs checkout and forwards the manual commit inputs to the action.When multiple open generated issues have the same title and source file, the oldest remains open and newer duplicates receive a linking comment and are closed with a duplicate relationship. Commit and line changes do not affect matching. Processing is scoped to the
need-fixlabel, preserves existing issue types, excludes pull requests, and reuses duplicate comments on retries. Personal repositories skip issue typing; an unavailableBugtype produces a warning while duplicate handling continues.The action uses the same shared Node.js CI configuration as
parse-ci-reports, including atest:ciscript that produces LCOV coverage. Documentation covers direct action use, workflow inputs, and matching rules. Inactivity management belongs to the separate Stale workflow.Validation completed locally:
make testnpm run test:ci --prefix actions/need-fix-to-issue— passes and generates LCOV coverage.make lint 'need-fix-to-issue|__shared-ci'The nine issue-management tests mock GitHub APIs and cover matching boundaries, existing issue types, unavailable types, API failures, and retries after partial failure.