Editorial standards

This page explains how the guides on Passing Build are produced, what is checked before they go live, and where the limits of those checks are.

How we write

Articles are drafted with the help of AI writing tools, following a written style guide.

What we check before publishing

• Every YAML workflow in an article is checked with actionlint.
• Python and JSON samples are syntax-checked.
• GitHub Actions referenced in samples are compared against their latest major release.
• Drafts are checked against excerpts from the official GitHub documentation.
• An editorial review pass fixes or removes claims it cannot support.

What we don't claim

• We do not run every sample in a live repository.
• The "Last reviewed" date on each article tells you when it was last checked. Behaviour can change after that date.

Corrections

Report errors through the Contact page. Corrections are applied as soon as they are confirmed, and the "Last reviewed" date is updated.

Independence

There is no sponsored content. Some articles contain affiliate links; they are marked and explained in our affiliate disclosure, and they never decide what we recommend. If we add advertising, ads will be clearly separated from editorial content.

Who we are

Passing Build is a Grayledge Press publication, written by the Grayledge Press Editorial Team. See the About page for more.