Skip to content

Tell agent that CI runs only for changed charms #70

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dwilding merged 1 commit into from
Sep 3, 2026
Merged

Tell agent that CI runs only for changed charms #70

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions .github/scripts/probe_issue.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -170,6 +170,18 @@ def runtime_context(repository: str, issue_number: int, branch: str) -> str:
difference is the configuration you changed — not structural differences \
between unrelated charms.

### Per-charm CI

Each charm has its own CI workflow (`.github/workflows/<charm>.yaml`) that \
triggers only when files under that charm's directory change. **CI runs only \
for charms you modified** — unchanged charms get no CI at all. This means:

- If you modify only kepler, only kepler's CI runs. Kosmos's CI does not run.
- If you modify kepler and kosmos, both CIs run independently.
- Do not describe an unchanged charm as a "control" or talk about what its CI \
will show — it won't have any CI to show. Only discuss CI outcomes for charms \
you actually modified.

### Project structure (per charm directory)

- `src/charm.py` — charm code using `ops.CharmBase`; entry point is \
Expand Down