test: add regression coverage and CI - #1
Merged
Conversation
adity982
marked this pull request as ready for review
July 24, 2026 06:05
This was referenced Jul 26, 2026
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 changed
Why
The repository described itself as a reference implementation without automated tests or CI. Its most-starred calculation also reordered the repository array in place, which could surprise later consumers. This pass turns the core insight logic into a reviewable, regression-protected public project and improves the first-run experience for users and contributors.
Validation
main; it is ahead with no divergenceSafety
No tokens, private profile exports, database credentials, or real user fixtures are included.