[PATCH 0/3] gitlab: Add issue templates

Peter Krempa pkrempa at redhat.com
Mon Nov 30 09:44:12 UTC 2020


On Mon, Nov 30, 2020 at 09:51:26 +0100, Pavel Hrdina wrote:
> On Fri, Nov 27, 2020 at 06:05:41PM +0100, Peter Krempa wrote:
> > On Fri, Nov 27, 2020 at 16:50:01 +0000, Daniel Berrange wrote:

[...]

> ------------------------------------------------------------------------
> 
> <!-- See https://libvirt.org/bugs.html#quality for guidance -->
> 
> ## Software environment
>  - Operating system:
>  - Architecture:
>  - kernel version:
>  - libvirt version:
>  - Hypervisor and version:
> 
> ## Description of problem
> 
> ## Steps to reproduce
> 1.
> 2.
> 3.
> 
> ## Expected behavior
> 
> ## Additional information
> 
> <!-- 
>   Please provide additional details. This list is not complete and
>   contains what we usually ask the reporter if missing:
> 
>    - XML configuration of VMs or other objects
>    - log files (please attach compressed archive if you can't find the relevant section)
>    - stack trace of the crashed binary
> 
>   See https://libvirt.org/kbase/debuglogs.html for details how to
>   configure debug logs.

Missing end of comment.

> 
> <!-- The line below ensures that proper tags are added to the issue. -- >
> /label ~bug

I like this as it explicitly asks for configs. Also a bonus is that it's
lean on comments at the top, which is shown first.

I think that we should add the note of commit being stripped to the
multiline comment though, to be a bit safer.




More information about the libvir-list mailing list