This looks really good. We have integration tests for github (but none for gitlab/gitea). Does the PRIVATE-TOKEN header apply to the public gitlab instance or only self hosted ones?

Codecov Report

Attention: Patch coverage is 0% with 39 lines in your changes missing coverage. Please review.

Project coverage is 38.21%. Comparing base (4cdbb49) to head (8447be9).
Report is 33 commits behind head on develop.

@@             Coverage Diff             @@
##           develop     #645      +/-   ##
===========================================
- Coverage    40.13%   38.21%   -1.92%     
===========================================
  Files          230      230              
  Lines        17066    17089      +23     
  Branches      2047     2045       -2     
===========================================
- Hits          6849     6531     -318     
- Misses        9860    10228     +368     
+ Partials       357      330      -27     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Also, I ran across some info saying GitLab "Private Tokens" have been deprecated (here's the changelog https://gitlab.com/gitlab-org/gitlab-foss/-/blob/10-2-stable/CHANGELOG.md#1020-2017-11-22) and that PAT's should be used now instead?

@caesay this is interesting. I thought that this would be the same thing effectively.
In my instance, I go to "Acccess Tokens"...

and create a new PAT...

...but that's the token I need to send using the PRIVATE-TOKEN header.

I'm also not aware of any difference between self-hosted and public instance of gitlab, as long as you're using a quite matching version (e.g. API Version 4, not sure how it was in 3 etc.)

Do you think we need another PR update?