Please, please, please still release your source if you don't mind! Especially for "random hacks" like a home brew bridge!
You have no idea how many tiny repos I have used for reference with those types of projects! In many cases your code might be the only working example.
You can put a big disclaimer in it, declare it a PoC, and just ignore issues if you'd like - the code doesn't even have to still be working, it's still cool and helpful!
If it's just a small script you can throw it up on GitHub Gist. People can still leave comments there, but you might feel less obligated to spend your time on those than if you see "[x] open issues" on your project.
You can also disable issues entirely on a project, if it's slightly larger than just one script. This, plus a disclaimer on the readme like "This was made solely for my personal use and I cannot provide support!" seems like an okay way to go about this.
I've written hacky one-offs before that other people used as a jumping-off point for something more serious, which is pretty cool to see. I'm always in favor of releasing your code for that reason, you never know if someone else will find it useful!
You have no idea how many tiny repos I have used for reference with those types of projects! In many cases your code might be the only working example.
You can put a big disclaimer in it, declare it a PoC, and just ignore issues if you'd like - the code doesn't even have to still be working, it's still cool and helpful!