Package maintainers and Hackage trustees are allowed to edit certain bits
of package metadata after a release, without uploading a new tarball.
Note that the tarball itself is never changed, just the metadata that is
stored separately. For more information about metadata revisions, please
refer to the
Hackage Metadata Revisions FAQ.
| No. |
Time |
User |
SHA256 |
| -r1 (gitlab-haskell-0.1.0.0-r1) |
2019-04-10T12:33:03Z |
RobStewart |
6b12986f4720a87782a367d2ab4dc3d162414ef3c23aa03f0c615588a8761111
|
|
Changed description
from This Haskell library queries and updates the database of a GitLab instance using the GitLab web API: <https://docs.gitlab.com/ee/api/>
An example that returns projects for which issue creation is enabled is:
> projectsWithIssuesEnabled :: IO [Project]
> projectsWithIssuesEnabled = runGitLab myConfig $ filter (issueEnabled . issues_enabled) <$> allProjects
> where myConfig = defaultGitLabServer
> { url = "https://gitlab.example.com"
> , token = "my_access_token" }
> issueEnabled Nothing = False
> issueEnabled (Just t) = t
Unsurprisingly, GitLab hosts this Haskell library: <https://gitlab.com/robstewart57/gitlab-haskell>
to This Haskell library queries and updates the database of a GitLab instance using the GitLab web API: <https://docs.gitlab.com/ee/api/>
Unsurprisingly, GitLab hosts this Haskell library: <https://gitlab.com/robstewart57/gitlab-haskell>
|
| -r0 (gitlab-haskell-0.1.0.0-r0) |
2019-04-10T12:31:13Z |
RobStewart |
b9cbd32afd30e2eb6ed4eae4aae53a800249568c41e56f521f662807d75ad38e
|
|
|