Clarify explicit vs implicit triggers and improve documentation #808
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.
This adds a new warning box explaining when implicit triggers are disabled, clarifies that
include/excludefilters don't change triggering events, and improves several explanations throughout the execution model documentation to reduce confusion about trigger behavior.✨ PR Description
Purpose: Improve trigger documentation by clarifying the difference between explicit and implicit triggering mechanisms in gitStream platform.
Main changes:
onparameter) completely override default implicit trigger behaviorGenerated by LinearB AI and added by gitStream.
AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Description using Guidelines Learn how