patches¶
What we need is a way to grab patches (diffs), the project, the issue tracker URL, any tags we want to specify for it, and then finally, a way to output it to different front ends (XML, JSON, HTML) so on.
How will it work¶
github API
pros: quicker than download full git / hg repositories
cons: only contributions made through pull requests are gathered.
version control
pros: most thorough
cons: requires (in the case of git, mercurial) downloading whole repositories, then searching them.
trackers
examples: bugzilla, github, gitlab
pros: can grab direct patches from version control where authors aren’t as easy to pluck out.
What users need to add¶
Most VCS / tracking systems use VCS. For using Github API, you need to use an API token.
History¶
Next release
- [Support]: Initial commit
\ Sort by:\ best rated\ newest\ oldest\
\\
Add a comment\ (markup):
\``code``
, \ code blocks:::
and an indented block after blank line