-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No way to select https://github.com/pylint-dev/pylint-pytest #2313
Comments
Hi @stdedos! Thanks for reporting. I'm afraid the fuzzy-matching is the behavior provided by GitHub API search repos endpoint. I can definitely tweak the behavior on Octochangelog side for searching a single repository when a repo full URL is entered. |
In the meantime, you can access this repo in the comparator by setting it directly through the querystring: https://www.octochangelog.com/compare?repo=pylint-dev%2Fpylint-pytest |
Yeah, that's what I did 😅 |
@Belco90 how about weighing the results, like this:
I assume most users of Octochangelog will be interested in the changes in popular projects like big (testing) frameworks, static site generators and other popular libraries and things. So that's why putting the popular stuff first is likely what most users want/expect. I don't know if this is do-able, or what the cost is in API-calls or compute time. 😄 |
@HonkingGoose I believe GitHub API endpoint for this search allows sorting by stars. That should improve the results. |
Sorting by stars sounds good! |
I've tested sorting by stars, but didn't help to display this repo in the results (and would change the sorting for many other searches). The fix will definitely be allowing to enter an exact repo with |
Describe the bug
Trying to select the https://github.com/pylint-dev/pylint-pytest repo is impossible.
Only hacking the URL works.
Give the steps to reproduce
...
What browsers are you seeing the problem on?
Chrome
Have you thought of a possible solution?
Yes
If you have thought of a solution, please tell us about it!
Please accept any of those inputs:
And, for the last two, the "answer" should be only one specific repo.
For the first one, please "tune down" your fuzzy-matching 😅 Those ones:
Are more or less definitely not candidates
Do you want to help fix the bug?
No
Is there anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: