Expand description
The data of the code hosts (docs/PLUGINS.md §4.5): what a host’s pull requests, checks, reviews and deployments are,
as the core and the plugins that serve a host (forge/*) both know them. They travel as JSON, in camelCase; a plugin
written in another language writes the same.
Structs§
- Check
- A check or a status of a pull request’s last commit (a CI job).
- Deployment
- A deployment in one of the repository’s environments.
- Identity
- Who an account is on its host, as its token says.
- Merge
Options - How a pull request of a repository may merge, as the repository’s settings say (ESC-62): the strategies they allow,
and whether the host merges by itself once the checks pass (GitHub’s « Allow auto-merge », Gitea’s protected
branch). Read by
Forge::merge_options. - Pull
Request - A pull request as its host tells it (kept with an agent’s data:
AgentMeta::prs). - Pull
Request Draft - A pull request (a merge request on GitLab) to open.
- Rate
Limit - How much of its calls a host leaves, as its answers say.
- RepoRef
- A repository on a code host: its namespace (owner, organization, GitLab group and subgroups, Bitbucket workspace) and its name.
- Review
- Review
Comment - A comment of a pull request, on one of its lines or not.
- Review
Draft - A review to publish on a pull request, as the user validated it.
- Review
Line - A comment on a line of a review to publish.
Enums§
- Check
State - Merge
Strategy - How a pull request merges.
- PrState
- Review
State
Constants§
- OPEN_
PRS - The most open pull requests of a repository a host lists (
forge/openPullRequests).