Michael Vorburger

@dandavison My git's output should be in UTF-8, based on this: ```bash $ locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= ```

> @dandavison My git's output should be in UTF-8, based on this: @dandavison actually, forget about guessing what encoding `git` is sending to `delta` - a friend of mine pointed...

https://github.com/tnozicka/openshift-acme works great! It would just be cool to have this work with the click of a "Get Certificate!" button built into OpenShift, just to save a long night of...

Instead of Pushover directly, probably to best is to integrate [Shoutrrr](https://containrrr.dev/shoutrrr) (incl. [Pushover](https://containrrr.dev/shoutrrr/v0.5/services/pushover/), and [others](https://containrrr.dev/shoutrrr/v0.5/services/overview/)).

FYI: According to https://github.com/oxsecurity/megalinter/blob/main/CHANGELOG.md#v750---2023-10-29, the #3024 fix made it into v750, but I'm [still seeing this problem here](https://github.com/www-learn-study/saraswati.learn.study/actions/runs/6712830158/job/18243212335?pr=11) - which was with `oxsecurity/megalinter@b48455a119cc28045eee8f1e9d0a542a85e71f4f # v7.5.0`... so seems like this is...

> Is there a repo-wide setting that overrides the values there , something in the likes of https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository? https://github.com/www-learn-study/saraswati.learn.study/settings/actions has standard: * Allow all actions and reusable workflows * Read...

> Doesn't have the posting comment problem! It is only a linter that reports a problem, devskim Yes agreed the posting comment problem is solved, but wasn't what this issue...

> Meanwhile.... you can fix the workflows in your repo haha ^^ https://github.com/www-learn-study/saraswati.learn.study/pull/11/commits/d87a15f83b0e287ae35fe20e8035505e40947376 fixed this, by adding the following to `.mega-linter.yml`: ```yaml SPELL_LYCHEE_FILTER_REGEX_EXCLUDE: (.github\|.vscode) ```

No of course above was not a valid 😈 regexp, but this did the trick (NB 2 fixes; escape dot but not escape bar): ```yaml SPELL_LYCHEE_FILTER_REGEX_EXCLUDE: (\.github|\.vscode) ```

According to https://github.com/spotbugs/discuss/issues/82, https://github.com/bazel-contrib/rules_jvm#spotbugs_test (also available on https://registry.bazel.build/modules/contrib_rules_jvm) is the way to go.