So, you've got a test in your Git repo for everything. You have unit tests, functional tests, linting for everything including your docs, you're shipping a directory containing your Git hooks that invoke all tests as needed, you've set the `core.hooksPath` option to that directory, and you even have a `commit-msg` hook running gitlint.

Now:

What do you put in your `AGENTS.md` to keep your AI coding assistant from running `git commit --no-verify`?

Do you know a note-taking app that

- is FOSS,
- ships with Ubuntu,
- runs with GNOME,
- uses Markdown,
- stores each note in a file, as opposed to chucking them in a database,
- integrates with LanguageTool for spelling and grammar checking,
- sorts notes chronologically by default,
- supports tagging and categorization?

If so, please drop a link below. Thank you!

#AskFedi

If your README.md contains an emoji in every heading, you might as well call it DONTREADME.md.

Because it's bound to be unreviewed LLM-generated drivel.

You know what's a fun exercise to try with your agentic coding assistant on your documentation, static web site, or README?

Feed it Orwell's Six Rules and then instruct it to edit your docs according to them.

What's your deprecator pitch for knowledge bases?

(Like an elevator pitch, but you're explaining in 30-60 seconds why it's a bad idea.)

Boosts and comments appreciated!

Happy One of The Greatest Concerts Of All Time Anniversary Day to all who celebrate.

https://en.wikipedia.org/wiki/The_Freddie_Mercury_Tribute_Concert

Excuse me, hello. Sorry to bother you.

Any Canadians reading this? Would you be so kind to answer this question, or boost it for reach perhaps?

Thank you.

Will Jeremy Hansen become Canada's next space icon?