Continue @tierra's issue-sync branch #138
Conversation
Extracted client_* config logic to GitHubMixin as well. It can now be used for any github.* config key, but mostly just helpful for "client_id", "client_secret", and "hook_secret".
- Creates a new ticket for all new pull requests. - Automatically attaches patch from pull request. - Attaches PR updates as new patches.
Also use DB variables for strings when necessary.
All issue and pull request comments are now posted to the appropriate tickets as well as inline patch comments.
|
@tierra @aaugustin could one (or both) of you take a look please? I'm not quite sure how to test it... (which is why I haven't taken the PR out of Draft Mode yet) |
...actually I guess if #139 gets merged first, that'd be enough for me to take this out of Draft Mode... |
|
It's been quite a long time since I originally wrote this 8 years ago. Since then, my only Trac instance I was planning to use it for has since been decommissioned, with issues just one-time imported directly into GitHub. So I'm not even using what I wrote here, hence not following up on this. Certainly feel free to complete the rest of this still. I just don't have the time or interest in helping with it though. |
I fixed the merge conflicts that
tierra:issue-synchad with master. Closes #75 (or at least it ought to). Note that I haven't actually tested this myself, all I did was solve the merge conflicts.