I tag all new issues that come as “Feature Request”, “Bug”, etc. and then as far as I’m concerned, unless I’m interested in the issue, my work is done.
Those then serve as an excellent roadmap for anyone who wants to contribute, but my projects are built for me and I work on the parts I want and need.
I also use GH automation to auto-close issues after a year. If no one cares enough to implement the change in a year, no one cares.
Your project is yours, feel free to ignore everyone else.
I find the use of “she” throughout your site when referring to an automated code process to be fairly strange. I suspect you’re trying to add levity and personality, but it’s an odd thing to assign gender to. Perhaps consider replacing those with “it”?
At the risk of pumping my own project, and recognizing that this is an untested methodology, I've just recently created this project to do exactly that:
Windows support is being tracked in issue #103 on GitHub. People have had success building from source. Automated Windows builds currently fail for reasons unknown.
It's highly likely this won't work as-is, unfortunately. Docker support is "experimental" at best and a lot more effort needs to be put into the Dockerfile.
If you want this functionality, I recommend not using it as-is, given the security vuln GitHub is currently reporting. Rather, anyone has my permission to copy the code verbatim into your project. It's a pretty simple gem.
It's common to look back in life and see that what was once a deliberate action was in fact a mistake. Not a mistake in the sense of an accidental occurrence, but in the sense that if one could do it over again, one would do it differently.
That's how the term "mistake" is used in this article.
No, the terms picosecond and micron are pretty integral to the process. Imagine using a propane torch to heat up the side of a single brick in an apartment building wall for a few seconds. The temperature change in that brick, considerable compared to all the others, will have effectively no impact on the building itself.
Those then serve as an excellent roadmap for anyone who wants to contribute, but my projects are built for me and I work on the parts I want and need.
I also use GH automation to auto-close issues after a year. If no one cares enough to implement the change in a year, no one cares.
Your project is yours, feel free to ignore everyone else.
I also highly recommend watching this talk by Pieter Hintjens a couple of times. It is brilliant https://m.youtube.com/watch?v=uzxcILudFWM
(I’m the creator of WTFUtil).