On Wed, Jul 3, 2019 at 8:59 PM Christoph Feck <cf...@kde.org> wrote:
>
> On 07/03/19 07:31, Jean-Baptiste Mardelle wrote:
> > Having used gitlab issues quiet a lot in the last months for Kdenlive, I
> > think it would be sad to completely disable them. Making them accessible
> > to project members/developers only seems like a good compromise.
> >
> > I like to use them as a development coordination tool, and for us it's a
> > good replacement for phabricator's boards. I also find them more
> > intuitive to use than phabricator, referencing an issue in a commit is
> > as simple as putting #issue_number, while I never manage to reference or
> > close phabricator tasks/diffs from commit messages despite checking the
> > online doc (but that's probably my fault so not a real argument)...
>
> Do our hook recognize a keyword to automatically close github issues?
> It would be nice if developers used a standard notation that is
> parsable by our scripts for automated change logs.

Much like with Phabricator, responsibility for this functionality
isn't handled by our hooks - it's handled by the software itself.
For Gitlab, please see
https://docs.gitlab.com/ee/user/project/issues/automatic_issue_closing.html

>
> --
> Christoph Feck
> KDE Bug Triaging Team
>

Cheers,
Ben

Reply via email to