Support ignoring incoming resources #16
Merged
Conversation
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
tnthornton
force-pushed
the
respect-ignores
branch
from
793cb9f to
932c3ca
Compare
branden
approved these changes
Aug 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description of your changes
This should be merged after #15 .
This changeset adds support for ignoring resources and simply returning early. This is helpful in operation workflows when noise is injected into the pipeline. Some examples:
WatchOperationand setting a watch on Events.WatchOperationand setting a watch on all pods.In these cases, without a preceding function identifying that the resource is unimportant and then communicating that later functions in the pipeline should be skipping/ignored, we could end up erroneously calling claude frequently.
I have: