I'm not sure if it would work here, but I have seen some issue templates,
e.g. for haskell-language-server on github[1], use comment markup in the
template.
e.g.
<!--
If you encounter a bug or you have a support question, please try to fill
out some of the information below.
Generally speaking, the information below is meant to help debugging issues
but is no prerequisite for opening an issue.
-->
This is not rendered on the web or email views, but is seen when editing.
Alan
[1] https://github.com/haskell/haskell-language-server/issues/new
On Tue, 23 Feb 2021 at 21:21, Richard Eisenberg
I'm happy with this direction, though I don't think we should expect that even capital letters will actually make people notice the text. One small change to suggest, below:
On Feb 23, 2021, at 11:14 AM, Simon Peyton Jones via ghc-devs < ghc-devs@haskell.org> wrote:
*Proposed new template* PLEASE REPLACE ALL OF THIS TEXT with a description of your merge request, including
* A description of what the Merge Request does. For a single-commit MR, a copy of the commit message is often perfect.
* A reference (e.g. #19415) to the ticket that led to this MR, and that describes the problem that this MR solves. Almost all MRs need a ticket, except the tiniest changes (e.g. code formatting) - A ticket describes a *problem* - A merge request describes a *solution* to that problem.
While you are encouraged to write a good MR Description, it’s not compulsory. You could just be putting up the MR to share with a colleague, for example.
But if you want (a) to get code reviews from others, or (b) to land the patch in GHC, please do follow these guidelines.
If you are not ready for wide review, please start the MR name with the prefix "WIP:", for "work in progress".
For general style guidance see https://gitlab.haskell.org/ghc/ghc/wikis/commentary/coding-style
Richard _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs