| Age | Commit message (Collapse) | Author |
|---|
|
Apparently forgejo has a more creative interpretation of \(\) than I was
hoping in their markdown parser and thought it was maths. I have no idea
then how you put a link in parens next to another square-bracket link,
but I am not going to worry about it.
There were several more typos, which I also fixed.
Fixes: https://git.lix.systems/lix-project/lix/issues/517
Change-Id: I6b144c6881f92ca60ba72a304ce7a0bcb9c6659a
|
|
We do not need a stale bot. We do not need dependabot.
Fixes: https://git.lix.systems/lix-project/lix/issues/391
Change-Id: I983fae4dc4cd9022b12f70e330b5c984c5fc1b9d
|
|
`nix --version` doesn't require `nix-command` experimental feature to
run and we could all do with less nix-env
Change-Id: I90748d591c574d96eda46591e9f9ce828311da29
|
|
These are not the way that we want to do things.
Change-Id: I5f3706cf50d007a6659edb96a6230d52e18a769a
|
|
it's annoying to write issues with the checklist in the way, and the
proposal is more important.
|
|
since the installer prompts users to file issues, labelling them
automatically should reduce triaging effort significantly.
|
|
decided on the @NixOS/documentation-team, see NixOS/nix.dev#359 for more information
|
|
according to [GitHub documentation] some fields are required.
`about` is not listed, but it probably is required.
[GitHub documentation]: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms
|
|
markdown would interpret parentheses as belonging to the first link without escaping.
|
|
this allows anyone to create labelled issues for easy filtering.
|
|
each change should be an improvement, a label for that is redundant.
|
|
|
|
|
