@@ -17,8 +17,14 @@ Before you submit a bug report, search the [open issues] *and* [closed issues]
1717to make sure the issue hasn't come up before. Also, check the [User's Guide] and
1818[FAQs] for anything relevant.
1919
20−Make sure you can reproduce the bug with the [latest released version] of pandoc
21−(or, even better, the [development version]).
20+Make sure you can reproduce the bug with the [latest released
21+version] of pandoc---or, even better, the development version,
22+since the bug may have been fixed since the last release.
23+[Nightly builds] are available, so you don't need to compile
24+from source to test againt the development version.
25+(To fetch a nightly, visit the link, click the topmost "Nightly"
26+in the table, then choose your platform under "Artifacts." Note
27+that you must be logged in with a GitHub account.)
2228
2329Your report should give detailed, *reproducible* instructions, including
2430
@@ -346,7 +352,7 @@ you may want to consider submitting a pull request to the
346352[open issues]: https://github.com/jgm/pandoc/issues
347353[closed issues]: https://github.com/jgm/pandoc/issues?q=is%3Aissue+is%3Aclosed
348354[latest released version]: https://github.com/jgm/pandoc/releases/latest
349−[development version]: https://github.com/pandoc-extras/pandoc-nightly/releases/latest
355+[Nightly builds]: https://github.com/jgm/pandoc/actions?query=workflow%3ANightly
350356[pandoc-discuss]: http://groups.google.com/group/pandoc-discuss
351357[issue tracker]: https://github.com/jgm/pandoc/issues
352358[User's Guide]: http://pandoc.org/MANUAL.html