rancher/k3k

Skip CI for some changes

Closed

#674 opened on Feb 17, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (77 forks)auto 404
good first issueteam/collietech-debt

Repository metrics

Stars
 (886 stars)
PR merge metrics
 (PR metrics pending)

Description

For some changes we should not trigger all the tests.

I.e. for docs changes we could just run the validate, or nothing (i.e. the README).

Contributor guide

Research direction
Identify the CI configuration file (e.g., .github/workflows/) and determine how to conditionally skip tests for documentation changes.
Tech stack
go
Domain
devopsci cd
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitCI/CD basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75