[DOCS-14116] Only run CI tests when a tested file or directory changes Created: 11/Jan/21 Updated: 04/Jan/23 Resolved: 12/Jan/21 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Realm |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Nicholas Larew | Assignee: | Nathan Contino (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 3 years, 4 weeks, 2 days ago |
| Epic Link: | DOCSP-13317 |
| Story Points: | 1 |
| Description |
DescriptionWe should only run tests if there's some change to test. We gain nothing by running tests on PRs/pushes where no tested examples changed & doing so wastes time & resources. We can update our GitHub Actions workflows to do this. SeeĀ Example including paths in the GitHub docs. e.g. for .NET we could update /.github/workflows/dotnet-core.yml as in the following: (can we combine the `paths` definitions for `push` and `pull_request` somehow?)
Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Nathan Contino (Inactive) [ 11/Jan/21 ] |
|
We only use "pull_request" events currently since the only thing that "push" gives us with our current workflow on top of that is a build after we've merged into master, which isn't super useful. So no need to worry about combining the definitions. |