Skip to content
Issue Triage

No conditional-visibility EXCLUDE rule can be created: isInclude=false is a boolean bound into a smallint column (400 on PostgreSQL = the CI default) #16

Sign in to view logs

No conditional-visibility EXCLUDE rule can be created: isInclude=false is a boolean bound into a smallint column (400 on PostgreSQL = the CI default)

No conditional-visibility EXCLUDE rule can be created: isInclude=false is a boolean bound into a smallint column (400 on PostgreSQL = the CI default) #16

Triggered via issue August 11, 2026 13:56
@rubenvdlinderubenvdlinde
opened #96 12fca7c
Status Failure
Total duration 19s
Artifacts –

issue-triage.yml

on: issues
triage  /  Preflight (PROJECT_TOKEN)
3s
triage / Preflight (PROJECT_TOKEN)
triage  /  Triage New Issue
0s
triage / Triage New Issue
triage  /  Handle Triage Decision
triage / Handle Triage Decision
triage  /  Backlog Triage Existing Issues
triage / Backlog Triage Existing Issues
Fit to window
Zoom out
Zoom in

Annotations

2 errors
triage / Preflight (PROJECT_TOKEN)
Process completed with exit code 1.
PROJECT_TOKEN is empty or was never passed
Issue Triage cannot run. The caller declares the secret, but the value that arrived is empty — so every downstream actions/github-script step would fail about a minute from now complaining about 'github-token', which is the action's input, not the missing thing. Add PROJECT_TOKEN to this repository's (or organisation's) secrets and make sure the caller forwards it, e.g. 'secrets: {PROJECT_TOKEN: \}' or 'secrets: inherit'.