Crate git_next_core

Modules§

message
newtype
pike
The pipe operator |> allows you to establish “pipelines” of functions in a flexible manner.
pike_opt
Works similar to pike but pike_opt keeps going as long as the proceding functions retuns None. Returns the first Some value.
pike_res
Works similar to pike but pike_res exits the pipeline early if a function returns an Err()
s
Converts the value into a String by calling the std::fmt::Display::to_string on the value.

ApiToken
The API Token for the user ForgeJo: https://{hostname}/user/settings/applications Github: https://github.com/settings/tokens
BranchName
The name of a Git branch
CommitCount
A number of commits
ForgeAlias
The name of a Forge to connect to
ForgeConfig
Defines a Forge to connect to Maps from git-next-server.toml at forge.{forge}
ForgeDetails
The derived information about a Forge, used to create interactions with it
ForgeNotification
A notification receive from a Forge, typically via a Webhook.
GitDir
The path to the directory containing the git repository.
Hostname
The hostname for the forge
RegisteredWebhook
RemoteUrl
The URL of a remote repository
RepoAlias
The alias of a repo.
RepoBranches
Mapped from .git-next.toml file at branches
RepoConfig
Mapped from .git-next.toml file in target repo Is also derived from the optional parameters in git-next-server.toml at forge.{forge}.repos.{repo}.(main|next|dev)
RepoPath
The path for the repo within the forge. Typically this is composed of the user or organisation and the name of the repo e.g. {user}/{repo}
ServerRepoConfig
Defines a Repo within a ForgeConfig to be monitored by the server Maps from git-next-server.toml at forge.{forge}.repos.{name}
User
The user within the forge to connect as
WebhookAuth
The unique token authorisation for the webhook.
WebhookId
The ID of the webhook, as returned by the forge when it is registered.