@tripleee Yeah, I probably would have only enabled one, but I've used my fork in order to test changes to the CI configs for all of the various CI platforms we use, so having them all enabled was necessary in order to not be testing those configs in the main repos.
@tripleee Thanks. We're aware of the issue. We're interested in still seeing new ones mentioning the library caught.
@Mithical Yes, that probably shouldn't happen. Please open a GitHub issue. It's an issue for both the charcoal-se.org code and MS. It could be masked out in the charcoal-se.org code, which would "fix" that display issue, but it could be considered a more general issue in that MS doesn't differentiate between mods and CMs. The MS issue might be resolved by just changing the documentation, given that MS doesn't, currently, have a need to differentiate between moderators and CMs.
@Mithical Actually, if you haven't created GitHub issues, don't worry about it. I took a brief look at it. There's an easy, general fix for the site (or at least it should work:) ), and it's using the V1 version of the MS API. It would probably still be reasonable for there to be more/better documentation, but that's a larger issue.
@Ethan That pattern looks like it's already caught by Potentially bad keyword in answer and Potentially bad keyword in body Append -force to the command word(s) if you really want to add the pattern you provided.
