Skip to content

Scope CI and deployment to the files they validate #41

Closed

Description

@dskvr

CI currently runs the full workspace/Tauri/package checks and two source AUR builds on every PR. Website, documentation and README changes should validate only their affected surfaces.

Acceptance:

  • Add declarative path filters for application CI, web/docs CI, AUR checks and docs deployment; retain the already-scoped VM checks with complete direct inputs.
  • Isolate lightweight workflow contract checks from native builds.
  • Preserve coverage for app/runtime/build/packaging changes and shared configuration changes.
  • Shared pnpm-lock.yaml edits must distinguish application dependencies from web-only dependencies; demonstrate that merged PR Give the landing page a minimal identity and reactive signal background #40 would skip native work.
  • Handle PR merge-base comparison, default-branch push ranges, deletions/renames, unknown lock formats and initial pushes conservatively.
  • Preserve deliberate manual, schedule and release-tag semantics. Do not change branch-protection settings.
  • Add regression tests for routing and workflow wiring; document the path ownership and required-check caveat.

Current live settings: master has no branch protection and the repository has no rulesets. No new external actions or project dependencies are needed; use Ruby YAML already required by workflow verification.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions