[GitlabIssueBridge] Add bridge #2760
Conversation
Pull request artifacts
|
|
gitlab has really good feeds so I assume they don't include issue and merge comments in their feed? Move the |
This tracks issue comments on arbitrary gitlab projects.
- Proper UIDs - Default bridge name fixed - Fix cache identifiers - Add TODOs
And prefer original author over editor.
Prettier without it.
This bridge can now generate feeds for Merge Requests.
Use gitlab.com if no h parameter was given. Fixes a phpunit test.
Just depend on rss-bridges built-in caching.
Exactly. They just don't have feeds for individual issues/MRs. The issues should be resolved (see the last three commits). I additionally rebased everything on master. |
|
The |
* [GitlabIssueBridge] new bridge This tracks issue comments on arbitrary gitlab projects. * [GitlabIssueBridge] Prepare for Merge Request support + fixes - Proper UIDs - Default bridge name fixed - Fix cache identifiers - Add TODOs * [GitlabIssueBridge] creation timestamp preferred And prefer original author over editor. * [GitlabIssueBridge] Do not add date to item title Prettier without it. * [GitlabIssueBridge] Support Merge Requests This bridge can now generate feeds for Merge Requests. * [GitlabIssueBridge] typo * [GitlabIssueBridge] Fix Img src attr in comments * [GitlabIssueBridge] Fix function call * [GitlabIssueBridge] Fix test Use gitlab.com if no h parameter was given. Fixes a phpunit test. * [GitlabIssueBridge] linting * [GitlabIssueBridge] Add MR support to description * [GitlabIssueBridge] Move function collectData * [GitlabIssueBridge] rm single-use class constants * [GitlabIssueBridge] Remove manual caching Just depend on rss-bridges built-in caching.
This bridge provides content for GitLab issues and merge requests, similar to the GithubIssueBridge.
Runs smoothly for ~two weeks for me.