Skip to main content

Module entire_forge

Module entire_forge 

Source
Expand description

Repositories hosted on Entire itself (/et/PROJECT/REPO) behind Host, through the entire CLI (see crate::entire), which finds its own login: jouet never handles an Entire token.

A trail is the PR, and its number the PR’s number. Its discussions are the review threads: each has a title, messages and replies, and can be resolved. Its review findings (the code_review discussions) are not listed here: pr threads lists them through crate::entire, as for a GitHub PR, with entire: handles. The checks are the trail’s check runs (Buildkite and the like) and one “Entire Gates” check made of its blocking gates, so a failing gate reads as it does on GitHub; the approvals gate is the review decision instead.

The CLI has no route to a commit’s files, the merge base or the branch’s commits, so those come from this clone’s git, and say so when it lacks the commit.

Structs§

EntireForge

Functions§

gates
The trail’s blocking gates as one Entire Gates check, the way the check GitHub shows reads them: failed if any fails, pending while any has not been evaluated, else passed. The approvals gate is left out, since it is the review decision. None when the trail has no other blocking gate.
runs
The trail’s check runs, as mergeability.checks.runs lists them.