-
Notifications
You must be signed in to change notification settings - Fork 1
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
Don't create multiple issues #19
Comments
Related #17 (comment) |
Hey guys, sorry for the duplicate issues! I'm actively trying to figure out the best way to dedup issues. The current solution is to check for existing issues (open or closed) that either
But unfortunately every time I update the deduplication hashes, it then causes pre-existing issues to not be recognized. So although I think the current system does a decent job, it did take a decent amount of trial and error to get here. I'm really sorry about the spam! I try to do my best to triage any issues as they get generated. |
Also, if you have any other ideas to improve the issue dedup'ing hashes, I'd be genuinely curious to hear! I'm open to any improvements to the system. |
I would suggest to use an extra repository right now. Then you can fidel with the code, test things and try to get the early bugs squashed out. If everything is battle tested and working to your likings it can be put live on nixpkgs. This way we can keep the disruption low and don't ping people unnecessarily. |
For the same failure the script creates new issues with every run it seems, e. g., like #169873.
If there is already an open issue then the script should pass that step or update the already present issue.
The text was updated successfully, but these errors were encountered: