dev: target master branch

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -16,7 +16,7 @@ body:
       + [ ] Search [the issue tracker](https://github.com/hlissner/doom-emacs/issues) for similar issues (the closed issues too).
       + [ ] Search [the Discourse](https://discourse.doomemacs.org) for any errors and solutions.
       + [ ] Ensure the issue can be reproduced on [the latest commit](https://github.com/hlissner/doom-emacs/commit) of Doom Emacs.
-      + [ ] Consult [our troubleshooting](https://github.com/hlissner/doom-emacs/blob/develop/docs/getting_started.org#troubleshoot) on techniques to get more information and, possibly, solve the issue yourself.
+      + [ ] Consult [our troubleshooting](https://github.com/hlissner/doom-emacs/blob/master/docs/getting_started.org#troubleshoot) on techniques to get more information and, possibly, solve the issue yourself.
 - type: textarea
   attributes:
     label: What did you expect to happen?
@@ -28,7 +28,7 @@ body:
     label: What actually happened?
     description: |
       + Include screenshots/casts, if possible
-      + List *all* error messages and **[include backtraces for each of them](https://github.com/hlissner/doom-emacs/blob/develop/docs/getting_started.org#how-to-extract-a-backtrace-from-an-error)
+      + List *all* error messages and **[include backtraces for each of them](https://github.com/hlissner/doom-emacs/blob/master/docs/getting_started.org#how-to-extract-a-backtrace-from-an-error)
       + Include any suspicious logs in the **[\*Messages\*](https://doomemacs.org/d/t/55) buffer.
       + If you include log dumps, please use [pastebin.com](https://pastebin.com)
       + **Use [code fences](https://docs.github.com/en/github/writing-on-github/creating-and-highlighting-code-blocks) for code, error messages, and backtraces.**