Asked for by the operator: a plan readable before merging. Given a repository and the files a branch changes (or the modules by name), plans --what-if owner/repo --paths a,b answers with the tiers the merge handler would produce — the modules those files touch, what packages their source, everything reachable along the dependency relation — and what each tier does: built and sent to its machines, or built and left because its policy records. Saved nowhere. On the seat as plans {repository, paths|modules}, so the console can take a PR's file list from the forge and show the plan. make check on the branch.
Asked for by the operator: a plan readable before merging. Given a repository and the files a branch changes (or the modules by name), `plans --what-if owner/repo --paths a,b` answers with the tiers the merge handler would produce — the modules those files touch, what packages their source, everything reachable along the dependency relation — and what each tier does: built and sent to its machines, or built and left because its policy records. Saved nowhere. On the seat as `plans {repository, paths|modules}`, so the console can take a PR's file list from the forge and show the plan. `make check` on the branch.
Given a repository and the files a branch changes (or the modules by name), plans answers with the tiers
the merge handler would produce — the modules those files touch, what packages their source, everything
reachable along the dependency relation — and what each tier does: built and sent to its machines, or
built and left because its policy records. Saved nowhere. On the seat as plans {repository, paths|modules}.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Asked for by the operator: a plan readable before merging. Given a repository and the files a branch changes (or the modules by name),
plans --what-if owner/repo --paths a,banswers with the tiers the merge handler would produce — the modules those files touch, what packages their source, everything reachable along the dependency relation — and what each tier does: built and sent to its machines, or built and left because its policy records. Saved nowhere. On the seat asplans {repository, paths|modules}, so the console can take a PR's file list from the forge and show the plan.make checkon the branch.Given a repository and the files a branch changes (or the modules by name), plans answers with the tiers the merge handler would produce — the modules those files touch, what packages their source, everything reachable along the dependency relation — and what each tier does: built and sent to its machines, or built and left because its policy records. Saved nowhere. On the seat as plans {repository, paths|modules}.