Crate git_next_core

source ·

Modules§

Macros§

  • The pipe operator |> allows you to establish “pipelines” of functions in a flexible manner.
  • Works similar to pike but pike_opt keeps going as long as the proceding functions retuns None. Returns the first Some value.
  • Works similar to pike but pike_res exits the pipeline early if a function returns an Err()

Structs§

  • The name of a Git branch
  • The name of a Forge to connect to
  • Defines a Forge to connect to Maps from git-next-server.toml at forge.{forge}
  • The derived information about a Forge, used to create interactions with it
  • A notification receive from a Forge, typically via a Webhook.
  • The path to the directory containing the git repository.
  • The hostname for the forge
  • The URL of a remote repository
  • The alias of a repo.
  • Mapped from .git-next.toml file at branches
  • 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)
  • 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}
  • Defines a Repo within a ForgeConfig to be monitored by the server Maps from git-next-server.toml at forge.{forge}.repos.{name}
  • The user within the forge to connect as
  • The unique token authorisation for the webhook.
  • The ID of the webhook, as returned by the forge when it is registered.

Enums§