Problem statement
The repository currently contains only one GitHub Actions workflow
(sync-project-priority-from-labels.yml) which is project-management related.
There is no CI workflow for code quality validation such as linting,
syntax checking, or import validation on pull requests.
As a result, pull requests merge without any automated quality gate.
All style and static analysis issues must be identified manually during review,
which increases review burden and risk of regressions.
Proposed solution
Add a minimal GitHub Actions workflow that performs Python linting
using Ruff.
Scope:
- Add a workflow file in
.github/workflows/
- Trigger on pull requests to
main
- Install Python
- Install Ruff
- Run
ruff check .
- Fail the workflow if lint errors are detected
This task is intentionally limited to linting only.
It does not introduce testing, packaging verification,
or a full CI/CD pipeline.
The goal is to establish a foundational automated quality gate
that can be extended in future work.
Acceptance criteria
Dependencies and constraints
- No upstream dependency required
- Does not modify application logic
- Must comply with repository contribution workflow
- Future CI extensions (tests, packaging verification) are out of scope
Problem statement
The repository currently contains only one GitHub Actions workflow
(
sync-project-priority-from-labels.yml) which is project-management related.There is no CI workflow for code quality validation such as linting,
syntax checking, or import validation on pull requests.
As a result, pull requests merge without any automated quality gate.
All style and static analysis issues must be identified manually during review,
which increases review burden and risk of regressions.
Proposed solution
Add a minimal GitHub Actions workflow that performs Python linting
using Ruff.
Scope:
.github/workflows/mainruff check .This task is intentionally limited to linting only.
It does not introduce testing, packaging verification,
or a full CI/CD pipeline.
The goal is to establish a foundational automated quality gate
that can be extended in future work.
Acceptance criteria
.github/workflows/mainDependencies and constraints