docs(ci): state that the CI checks on main are advisory #619

Merged

hexajon merged 1 commit from issue-499-ci-checks-advisory into main 2026-09-24 15:27:54 +00:00

Conversation 0 Commits 1 Files changed 1 +3 -2

hexajon commented 2026-09-24 15:27:52 +00:00

Owner

Copy link

Summary

A comment in ci.yml said the (pull_request) contexts were required branch-protection checks. Branch protection on main requires no CI check, and that is the intended setting: the CI checks stay advisory, and the local gate is the barrier before a merge. The comment now says so.

It is a comment-only change: the parsed workflow is identical before and after. I also ran the gate job's install system deps and dedup check steps in the job's pinned golang:1.27-trixie image as a push event. Both exited 0, and dedup wrote skip=false.

Closes #499

Closes #499

## Summary A comment in `ci.yml` said the `(pull_request)` contexts were required branch-protection checks. Branch protection on `main` requires no CI check, and that is the intended setting: the CI checks stay advisory, and the local gate is the barrier before a merge. The comment now says so. It is a comment-only change: the parsed workflow is identical before and after. I also ran the gate job's `install system deps` and `dedup check` steps in the job's pinned `golang:1.27-trixie` image as a push event. Both exited 0, and `dedup` wrote `skip=false`. Closes #499 Closes #499

hexajon added 1 commit 2026-09-24 15:27:52 +00:00

docs(ci): state that the CI checks on main are advisory ... 01f3e6f45d

Closes #499

hexajon merged commit 01f3e6f45d into main 2026-09-24 15:27:54 +00:00

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

breaking

Breaking change - flag for release notes

  

bug

Something is not working

  

documentation

Documentation only

  

enhancement

New feature

  

epic

Tracking epic with dependency children

  

good first issue

Interested in contributing? Get started here.

  

help wanted

Maintainer would welcome outside help

  

refactoring

Code restructuring without behavior changes

  

resolution/duplicate

Closed as duplicate of another issue

  

resolution/invalid

Closed as invalid or not reproducible

  

resolution/wontfix

Closed as won't fix

  

security

Security issue or hardening

  

severity/critical

Security severity: critical

  

severity/high

Security severity: high

  

severity/low

Security severity: low

  

severity/medium

Security severity: medium

  

status/abandoned

Someone started, then walked away - up for grabs

  

status/blocked

Blocked by another issue or an external dependency

  

status/needs-decision

Waiting on a maintainer decision; workable once decided

  

status/needs-info

Waiting on reporter / more information before work can start

  

status/needs-verification

Done except verification in a live interactive session

  

testing

Test suite / CI infrastructure work

  

upstream

Related to an upstream repository, already reported there

No labels

breaking

bug

documentation

enhancement

epic

good first issue

help wanted

refactoring

resolution/duplicate

resolution/invalid

resolution/wontfix

security

severity/critical

severity/high

severity/low

severity/medium

status/abandoned

status/blocked

status/needs-decision

status/needs-info

status/needs-verification

testing

upstream

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

sixfold-space/madtea!619

No description provided.