You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A GitHub token is already accepted as CLI argument. But I don't see what it translates to in terms of HTTP request.
See https://docs.gitlab.com/ee/api/repository_files.html#get-raw-file-from-repository for how to access a raw file from a private project. I'm not sure that is appropriate for my use case: I simply hyperlink to private project landing pages, which are flagged by Lychee under CI.
The text was updated successfully, but these errors were encountered:
sanmai-NL
changed the title
Support GitLab CI token to access private projects
Support GitLab token to access private projects
Oct 10, 2023
Gitlab is currently not supported, but we can add a gitlab_token argument similar to GitHub.
Contributions welcome. I'm not sure when I would get the opportunity to add this myself.
The GitHub token gets passed to the GitHub crate, octokit. That's the only place where it gets used. However, for gitlab, we can start to pass it as a header if it's a gitlab URL.
I tested and found that specific support for GitLab is unnecessary, using the --header CLI/configuration parameter PRIVATE-TOKEN=.... However, this is not usable yet for our applications in CI, due to #1297 and in particular #1298.
A GitHub token is already accepted as CLI argument. But I don't see what it translates to in terms of HTTP request.
See https://docs.gitlab.com/ee/api/repository_files.html#get-raw-file-from-repository for how to access a raw file from a private project. I'm not sure that is appropriate for my use case: I simply hyperlink to private project landing pages, which are flagged by Lychee under CI.
The text was updated successfully, but these errors were encountered: