Tell agent that CI runs only for changed charms - #70
Merged
Conversation
Each charm has its own CI workflow that triggers only when files under that charm's directory change. The agent didn't know this, so it described unchanged charms as 'controls' and talked about what their CI would show — but unchanged charms get no CI at all. Added a 'Per-charm CI' section to the charm development context explaining this, with explicit guidance: only discuss CI outcomes for charms you actually modified.
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
1 participant
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.
Each charm has its own CI workflow that triggers only when files under that charm's directory change. The agent didn't know this, so in PR #69 it described kosmos (an unchanged charm) as a 'control' and talked about what its CI would show — but unchanged charms get no CI at all.
Added a 'Per-charm CI' section to the charm development context explaining this, with explicit guidance: only discuss CI outcomes for charms you actually modified.