Push without starting a run: [skip flow] in the change's message issue #284 closed: completed andymccall opened this 15 days ago · 0 comments

A push always starts a run of every unscoped job. The forges' convention is a marker in the commit message; ours is signed, so who skipped is verifiable.

• [skip flow], [skip ci] or [ci skip] (any case) in the message of the newest change a push brings: no jobs; a run is recorded as skipped, saying which change and who pushed it, so the gap shows on the run list.
• Tags always run (releases).
• Settings › Runs: where skipping is allowed: any bookmark (default), every bookmark but the default one, or never.
• A skipped push's changes count as untested: the next run's scope covers them.