Skip to content

[trial, do not merge] CI checks workflow - #2

Closed
srikoushik wants to merge 2 commits into
ci-trial-basefrom
ci-trial-checks
Closed

srikoushik wants to merge 2 commits into
ci-trial-basefrom
ci-trial-checks

Conversation

@srikoushik

Copy link
Copy Markdown

Temporary PR in the fork to trial the CI workflow before proposing it upstream. Will be closed after the run.

@srikoushik
srikoushik force-pushed the ci-trial-checks branch 4 times, most recently from 49426c2 to 5b97274 Compare November 4, 2026 06:43
srikoushik and others added 2 commits November 4, 2026 12:43
Nothing runs on pull requests today, and dev already has 38 failing
tests and 137 ruff findings, so a new problem is hard to spot by eye.
core-stack-org#1419 and core-stack-org#1420 show the cost: a repeated dict key (ruff F601) and then
a regression that an existing test caught, both merged unnoticed.

Add a "Checks" workflow for pull requests into dev and main. Each job
compares the pull request with its target branch and fails only on
what the pull request adds, so existing problems don't block anyone and
no list of known failures has to be maintained:

- lint: ruff 0.17.3 with bug-catching rules only (syntax errors,
  repeated dict keys, redefinitions, undefined names), counted per file
  and rule;
- tests: runs in the published ghcr.io/core-stack-org/core-stack-backend
  image with a Postgres service, generates migrations the way
  database-init.sh does, runs `manage.py check`, then the suite on both
  branches, and fails if a test fails only on the pull request.

Settings get placeholder values and a throwaway Fernet key; no secrets
are needed. The workflow only reports a status; whether it blocks
merging is a branch-protection setting for the maintainers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@srikoushik

Copy link
Copy Markdown
Author

Trial finished; the workflow is proposed upstream in core-stack-org#1447.

@srikoushik srikoushik closed this Nov 4, 2026
@srikoushik
srikoushik deleted the ci-trial-checks branch November 4, 2026 07:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant