Crate sandogasa_gitlab

Expand description

GitLab REST and GraphQL API client for issues and work items.

Structs§

Assignee: A GitLab user (assignee).
Client: Client for the GitLab REST API v4.
Event: One entry from the user-activity events endpoint. Fields are sparse — GitLab only populates the ones relevant to each action_name.
EventNote: Note payload attached to commented on events.
EventPushData: Push payload attached to pushed to / pushed new events.
GroupClient: Client for group-level GitLab API queries.
GroupProject: A project name returned by the GitLab group projects API.
Issue: A GitLab issue.
IssueUpdate: Parameters for editing an issue.
MergeRequest: A GitLab merge request (minimal fields).
ProjectSummary: Minimal project identity: what you need to filter events by path_with_namespace prefix and render a human-readable link.
User: A GitLab user as returned by /users?username=<name>.

count_authored_commits: Count commits in project_id authored by author within [since, until] (inclusive). GitLab’s commits endpoint matches the author parameter against both name and email fields, so passing the GitLab username usually works; if the user authored commits under an email only, pass that email string instead.
list_group_projects: List all projects under a GitLab group (public, no auth needed).
package_from_issue_url: Extract the package name from a GitLab issue or work item web_url.
parse_issue_url: Parse a GitLab issue / work-item URL into its components.
parse_mr_url: Parse a merge request URL into its components.
parse_project_url: Parse a GitLab project URL into (base_url, project_path).
project_path_from_issue_url: Extract the project path from a GitLab issue or work item web_url.
project_summary: Look up a project’s path_with_namespace from its numeric ID. Used to map event project_id → group-prefix filter.
user_by_username: Look up a user by username on a specific GitLab instance. Returns Ok(None) if the server returns 200 with an empty list (no user with that name on that instance).
user_events: Fetch a user’s activity events within [after, before) — GitLab’s event endpoint is half-open on both sides and rejects both-null. Results are paginated at 100/page; this follows every page until a short page arrives.
validate_token: Check whether a token is valid by calling GET /api/v4/user.