Documentation

runs a GitLab action.

Internally, this creates a single Manager, whichs keeps track of open connections for keep-alive and which is shared between multiple threads and requests.

An example of its use is:

projectsWithIssuesEnabled :: IO [Project] projectsWithIssuesEnabled = runGitLabyConfig $ filter (issueEnabled . issues_enabled) <$> allProjects where myConfig = defaultGitLabServer { url = "https://gitlab.example.com" , token = "my_access_token" } issueEnabled Nothing = False issueEnabled (Just b) = b

The same as runGitLab, except that it prompts for a GitLab access token before running the GitLab action.

In this case you can just use defaultGitLabServer with no modification of the record field values, because these values will be asked for at runtime:

runGitLabPassPrompt defaultGitLabServer myGitLabProgram

Only useful for testing GitLab actions that lift IO actions with liftIO. Cannot speak to a GitLab server. Only useful for the gitlab-haskell tests.

The same as runGitLab, except that it also takes a connection manager as an argument.