@tripleee I don't have a problem with you copying it and having it available somewhere. I'm happy to provide a different license for it, if you want one or if that helps. I'd normally choose the MIT license for most open source code. At a minimum, it's under CC BY SA 4.0, so you, or anyone, can copy it. Hmmm...
I hereby grant a license under the MIT license (modified such that the license text can be included by reference), for all bookmarklets which I have published on Stack Exchange chat (any of chat.stackoverflow.com, chat.stackexchange.com, or chat.meta.stackexchange.com) and future bookmarklets I publish on those sites, unless I revoke offering such licenses or explicitly exclude offering such licenses for a specific bookmarklet.
Overall, having a collection of bookmarklets seems like it would be a good idea. However, where you have them at the moment doesn't seem all that accessible for the project. Maybe on the SD or Charcoal wiki? A Charcoal Teams question with bookmarklets as answers? something/somewhere else???
@Makyen that's probably a better option, I wanted to publish my own (and the license is a CC one, because that's what Github recommended) and did not think it made sense at the time to put them in the Charcoal project's stuff; but the charcoal-se site / wiki seems like a good place going forward
Even with the disclosure, rapid-fire promotion of your software risks attracting negative attention and spam flags. Please review How to not be a spammer. — tripleee6 secs ago
@tripleee I handle doing the CI tests prior to pushing to the Charcoal repository in a couple of ways. First, my local local repository on my own machine is able to run the CI tests. It's been a long time since I set that up, but, IIRC, there wasn't much I needed to do to set it up beyond having Python installed, installing the requirements.txt and user_requirements.txt dependencies, which could be in a venv if desired, and then use the run_tests.sh script, or a slightly modified version of it, to run the tests.
The other way is that I forked the Charcoal repo into my own GitHub account and enabled GitHub Actions and CircleCI on my fork. I then push to my fork first, let the CI run, and then push to the main Charcoal repo once I'm sure the CI passes. Sometimes I cut corners and skip some of the testing steps, but fairly often that ends up with things not passing (which is more likely, due to me being in a hurry :; ).
@tripleee Thanks. I'll take a look.
I then create the PR from the branch I push to the Charcoal repo. As I recall, there was an issue with the CI tests not running on the PR, or not running quite the same, when I created the PR from a branch in my fork on GitHub. That was quite a while ago now, so the issue may have been resolved or no longer relevant. I don't recall if it was an issue with GH Actions, CircleCI, or Travis CI.
