[Gramps-devel] Bug tracker GitHub integration

[Nick Hall]

Devs,

I have enabled the Mantis bug tracker source integration.

You will see a "Repositories" option in the main menu. This allows you
to browse changesets. Unfortunately, only a small number of commits
were imported.

You can link to changesets, diffs and pull requests within notes using
the following syntax:

c:gramps:<commit>:

d:gramps:<commit>:

p:gramps:<pr>:

Bug reports can also be closed automatically. Rather than including a
bug number on the first line of the commit message please include one of
the following at the end of the commit message:

Fix #nnnnn. Fixes #nnnnn. Fixed #nnnnn.

Resolves #nnnnn. Resolved #nnnnn.

where nnnnn is the bug number.

Multiple bugs can be closed by specifying a list of bug numbers.

A note of the format "Fix committed in <branch> [<commit>]." will also
be added to the bug report.

It is also possible to link bugs to changesets using the keywords
bug(s), issue(s) or report(s).

Here are a few example bugs:

https://gramps-project.org/bugs/view.php?id=9984

https://gramps-project.org/bugs/view.php?id=9130

https://gramps-project.org/bugs/view.php?id=7532

The documentation is poor and I don't think everything is working
correctly yet.

This looks like a potentially useful feature. Let me know what you think.

Regards,


Nick.

[Josip]

Post by Nick Hall
Devs,
I have enabled the Mantis bug tracker source integration.
You will see a "Repositories" option in the main menu. This allows you
to browse changesets. Unfortunately, only a small number of commits
were imported.
You can link to changesets, diffs and pull requests within notes using
Bug reports can also be closed automatically. Rather than including a
bug number on the first line of the commit message please include one of
Fix #nnnnn. Fixes #nnnnn. Fixed #nnnnn.
Resolves #nnnnn. Resolved #nnnnn.
where nnnnn is the bug number.
Multiple bugs can be closed by specifying a list of bug numbers.
A note of the format "Fix committed in <branch> [<commit>]." will also
be added to the bug report.
It is also possible to link bugs to changesets using the keywords
bug(s), issue(s) or report(s).
https://gramps-project.org/bugs/view.php?id=9984
https://gramps-project.org/bugs/view.php?id=9130
https://gramps-project.org/bugs/view.php?id=7532
The documentation is poor and I don't think everything is working
correctly yet.
This looks like a potentially useful feature. Let me know what you think.
Regards,
Nick.

Very cool!

Can please other branches like gramps50 or gramps42 be added to "Primary
Branches" in "Update Repository".

Docs says that exist both "Import Last Data" and "Import Everything" in
"Manage Repository" panel, maybe second one will import more commits.
Also find in second doc that you may have to run this process more than
once to get it all.

docs are from
https://github.com/mantisbt-plugins/source-integration/blob/master/docs/CONFIGURING.SourceGithub.md
or more graphical one
http://docs.devzing.com/mantisbt-github-integration/

[Nick Hall]

Post by Josip
Can please other branches like gramps50 or gramps42 be added to
"Primary Branches" in "Update Repository".

The primary branches are now set to "master,gramps50,gramps42". I had a
space after the comma before.

I have also enabled branch mapping which should set the fixed in version.

I've set an option to assign the bug to the committer. I think that the
author would be better, but I can change it again later.

Post by Josip
Docs says that exist both "Import Last Data" and "Import Everything"
in "Manage Repository" panel, maybe second one will import more commits.
Also find in second doc that you may have to run this process more
than once to get it all.

I did use "Import Everything". Perhaps this is a rate limiting issue.


Nick.

[Nick Hall]

Post by Nick Hall
The primary branches are now set to "master,gramps50,gramps42". I had
a space after the comma before.

In writing this I just realised my mistake. It should be "
master,maintenance/gramps50,maintenance/gramps42".

Nick.

[Josip]

Post by Nick Hall

Post by Nick Hall
The primary branches are now set to "master,gramps50,gramps42". I had
a space after the comma before.

In writing this I just realised my mistake. It should be "
master,maintenance/gramps50,maintenance/gramps42".

I was just ready to post about this when thing suddenly start to works.

Also noticed that commit title get "(#XXX) added probably automatically
by github and bugtracker interpret that as bug-number instead of
pull-request.

See for example
https://gramps-project.org/bugs/plugin.php?page=Source/view&id=111