docs(ci): add change-aware workflow issue specs#1745
Merged
josecelano merged 1 commit intoMay 8, 2026
Conversation
Member
Author
|
ACK c027708 |
There was a problem hiding this comment.
Pull request overview
Adds finalized issue specification documents for the “change-aware CI” EPIC and its two implementation subissues (docs-only CI fast path and persistence-workflow scoping). These specs are part of the repository’s docs/issues tracking for planned CI optimizations.
Changes:
- Add EPIC spec for making CI change-aware (#1742).
- Add docs-only CI fast path spec (#1743).
- Add persistence-scoped workflow trigger spec (#1744).
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 10 comments.
| File | Description |
|---|---|
| docs/issues/1742-ci-change-aware-workflows-epic.md | Adds the EPIC spec documenting goals, scope, risks, and links to subissues/workflows. |
| docs/issues/1743-docs-only-ci-fast-path.md | Adds the docs-only CI fast-path subissue spec and acceptance criteria. |
| docs/issues/1744-scope-persistence-workflows-by-path.md | Adds the persistence workflow scoping subissue spec and acceptance criteria. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+27
to
+30
| - [`.github/workflows/testing.yaml`](../../../.github/workflows/testing.yaml) | ||
| - [`.github/workflows/os-compatibility.yaml`](../../../.github/workflows/os-compatibility.yaml) | ||
| - [`.github/workflows/db-compatibility.yaml`](../../../.github/workflows/db-compatibility.yaml) | ||
| - [`.github/workflows/db-benchmarking.yaml`](../../../.github/workflows/db-benchmarking.yaml) |
|
|
||
| - [#1726](https://github.com/torrust/torrust-tracker/issues/1726) is an evidence-driven research | ||
| issue about Rust compilation costs and whether `sccache` should be adopted at all. | ||
| - [#1740](../1740-fix-container-workflow-caching.md) addresses container build cache behavior. |
Comment on lines
+165
to
+168
| - [`.github/workflows/testing.yaml`](../../../.github/workflows/testing.yaml) | ||
| - [`.github/workflows/os-compatibility.yaml`](../../../.github/workflows/os-compatibility.yaml) | ||
| - [`.github/workflows/db-compatibility.yaml`](../../../.github/workflows/db-compatibility.yaml) | ||
| - [`.github/workflows/db-benchmarking.yaml`](../../../.github/workflows/db-benchmarking.yaml) |
| ## Problem | ||
|
|
||
| Documentation changes currently trigger the same expensive workflows as code changes, including | ||
| the `Testing` workflow in [`.github/workflows/testing.yaml`](../../../.github/workflows/testing.yaml). |
Comment on lines
+102
to
+105
| - Related workflow: [`.github/workflows/testing.yaml`](../../../.github/workflows/testing.yaml) | ||
| - Related workflow: [`.github/workflows/os-compatibility.yaml`](../../../.github/workflows/os-compatibility.yaml) | ||
| - Related workflow: [`.github/workflows/db-compatibility.yaml`](../../../.github/workflows/db-compatibility.yaml) | ||
| - Related workflow: [`.github/workflows/db-benchmarking.yaml`](../../../.github/workflows/db-benchmarking.yaml) |
Comment on lines
+12
to
+13
| - [`.github/workflows/db-compatibility.yaml`](../../../.github/workflows/db-compatibility.yaml) | ||
| - [`.github/workflows/db-benchmarking.yaml`](../../../.github/workflows/db-benchmarking.yaml) |
Comment on lines
+31
to
+33
| The database compatibility jobs in | ||
| [`.github/workflows/db-compatibility.yaml`](../../../.github/workflows/db-compatibility.yaml) | ||
| run `cargo test -p bittorrent-tracker-core ... run_mysql_driver_tests` and |
Comment on lines
+63
to
+64
| - [ ] Update [`.github/workflows/db-compatibility.yaml`](../../../.github/workflows/db-compatibility.yaml) | ||
| so it only runs for persistence-relevant changes. |
Comment on lines
+70
to
+71
| - [ ] Update [`.github/workflows/db-benchmarking.yaml`](../../../.github/workflows/db-benchmarking.yaml) | ||
| so it only runs for persistence-relevant changes. |
Comment on lines
+92
to
+93
| - Related workflow: [`.github/workflows/db-compatibility.yaml`](../../../.github/workflows/db-compatibility.yaml) | ||
| - Related workflow: [`.github/workflows/db-benchmarking.yaml`](../../../.github/workflows/db-benchmarking.yaml) |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #1745 +/- ##
===========================================
- Coverage 79.41% 79.40% -0.01%
===========================================
Files 368 368
Lines 27129 27129
Branches 27129 27129
===========================================
- Hits 21544 21543 -1
Misses 5310 5310
- Partials 275 276 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/issues/drafts/into final numbered pathsValidation
linter markdownRelated