Skip to main content
A blocked Tylon card
This card is blocked, which is the state worth showing first — a card that moves cleanly has nothing to explain.

​
The refusal is the provider’s own words

Required status check “contract-tests” is expected. GitHub refused the merge: the branch is 4 commits behind main and the branch protection rule on main requires branches to be up to date before merging.
Tylon did not summarise that or translate it into a status. It asked GitHub to merge, GitHub said no, and this is what it said. Underneath: the card stayed where it was. Nothing half-happened.

​
One card, three repositories

one is red — none of them move. Two of three green is not two thirds of a delivery, and a board that let this one through would be a board saying “shipped” about something that is half out.

​
When nothing is wrong

A Tylon card
The same card with nothing in its way: the repositories, their branches and their pull requests, and no banner. Most cards look like this — the blocked one is above because it is the state that has something to say.

​
Properties

Status, assignee, priority, feature, due date, labels. Under the status, again, what that stage does to Git — does not touch Git here, because In review is a stage that waits rather than merges.

​
The tabs

A person who does not write code can read all four. That is the point of them being here rather than a link to the forge.