From now on, our documentation will assume your Emacs config lives in
~/.config/emacs, by default, rather than ~/.emacs.d. Support for the
latter is not going away, it will simply be mentioned less in the
literature, as all supported versions of Emacs going forward (and future
versions of Doom) will support (and prefer) XDG conventions.
The user manual will be updated separately.
Close: #6965
Co-authored-by: gagbo <gagbo@users.noreply.github.com>
- Adds back a checklist, to pressure folks to do their homework.
- De-emphasizes pastebin in the system info.
- Revises instructions and postamble for brevity and simplicity. I hope
less reading to do will translate into more of it being read!
This removes the feature and bump request templates, as our issue
tracker will no longer accept them. They should either be submitted to
our Discourse/Discord, or come in the form of a pull request (as a proof
of concept proposal/RFC), or a bug report (in case a bump is needed to
address a bug).
Ref: https://discourse.doomemacs.org
Ref: https://doomemacs.org/discord
It'll be another week or two before our Discourse and new docs are
ready, and signing up for Discourse seems to be the end of the world for
some people, so I've replaced the discourse links with gists or links to
our old docs.
Too many people not modifying the title and now my inbox is full of
"Briefly summarize your issue" issues. At least when it's blank by
default, Github won't let you submit it until you fill it out.
The user's doom/info is essential information for debuggin issues.
Please don't modify or omit parts of it. Of course, feel free to remove
sensitive information, but do so selectively. The more you omit, the
less I have to work with.
Mistook exempt-{milestones,assignees} for
exempt-all-{milestones,assignees}. If an issue/PR is assigned one, it
means it's been approved/accepted, and I'll get around to it.
- Was formerly processing the internal merge commit, which never conforms
to our conventions, but is also unrelated to the work at hand.
- Now lints the range of commits applicable to the event, and not just
the latest commit.
Experimenting with an internal linter. Only trouble is, if Doom's CLI is
ever in a broken state, a contributor will have to know about
--no-verify option for git commit. This can be improved post CLI
rewrite.
