Uses the GitHub API (v3) to access and display issues from the bug tracker
Deze uitbreiding is al meer dan 2 jaar niet meer geupdated. Misschien worden hij niet langer onderhouden of ondersteund. Er kunnen compatibiliteitsproblemen zijn.
Vergelijkbaar met issuelinks
Allows the insertion of a table showing issues from the bug tracker on a GitHub repository. Filtering by state (open/closed/all) and label are supported. The table shows issue number, title, any labels (with their assigned colors) as well as creation date/time and creator.
Each issue title is also a link to the appropriate issue page on GitHub, and there is a link to the table's equivalent issues search in the footer of the table.
GitHub API responses are cached locally and the table is only updated when upstream changes occur.
Search and install the plugin using the Extension Manager. Refer to Plugins on how to install plugins manually.
Below are code snippets and static screenshots of the plugin's output with data from the DokuWiki Repository on GitHub1).
{{ghissues dokuwiki/Dokuwiki state:all label:feature}}
Basic syntax:
{{ghissues <repository> [state:<all|open|closed>] [label:<label1,label2,label3>]}}
Specifically:
{{ghissues
(required) marks the start<repository>
(required) gives the repository whose issues you'd like to list. Given in user/repo
format, e.g. ZJ/ghissues
state:<>
(optional) Case sensitive. state:
indicates you'd like to filter by state, and <>
can be followed by one of (all lowercase):all
open
closed
label:<>
(optional) comma-separated list of labels to filter by. Labels are filtered using AND, i.e. on issues with both label1
AND label2
would be shown if you entered label:label1,label2
. There should be no space between the last label and the closing braces}}
(required) closes the pattern.Three user settings are available.
GitHub allow authentication via personal OAuth tokens which can be generated at https://github.com/settings/applications. This is nice because it avoids having to provide a username/password combination. You can also control which parts of your account a token has access to.
Short answer: probably not. There are two reasons to use one:
This plugin does its best to minimize the number of requests it makes. It implements cacheing on DokuWiki's side together with conditional HTTP requests. The quick-and-dirty rule is that you'll generate 1 request per unique table per change to an issue on GitHub's side.
See https://github.com/ZJ/ghissues/commits/master