GitLab Executor
To use this tool, it is required to have a GitLab account somewhere. In the GitLab, a personal access token needs to be created. The respective page can be found under https://<gitlab.domain.com>/profile/personal_access_tokens. Enter a name for your new access token and check the api box. If only read-only access is desired, read_api is sufficient. Keep the access token safe as it will only be displayed once.
In order to provide the access token and base url of the GitLab to gitlab-x either use environment variables or pass them as command line options:
GITLAB_AT can be used to provide the access token
GITLAB_URL can be used to provide the base url of the GitLab
export GITLAB_AT=asdf1234
export GITLAB_URL=https://gitlab.com
If no environment varialbe is given for the access token or base url, they need to be provided as command line arguments:
-u or --url followed by the GitLab URL
-t or --access-token followed by the access token
npm gitlab-x -u gitlab.com -t asdf1234 version
FAQs
GitLab Executor API Interface
The npm package gitlab-x receives a total of 4 weekly downloads. As such, gitlab-x popularity was classified as not popular.
We found that gitlab-x demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
React's CRA deprecation announcement sparked community criticism over framework recommendations, leading to quick updates acknowledging build tools like Vite as valid alternatives.
Security News
Ransomware payment rates hit an all-time low in 2024 as law enforcement crackdowns, stronger defenses, and shifting policies make attacks riskier and less profitable.
Security News
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.