Unclear behaviour of filters on pipeline page
- Dominant language
- Ruby
- Stars
- 59
- Forks
- 313
- PR merge metrics
- No merged PRs in 30d
Description
Hello
I recently started using the "Filter builds using a conditional" pipeline-level setting, but due to its location I thought builds matching the expression would be triggered *in addition to* the things selected below (Pull Request, push, tag), rather than filtering them.
I think it would be good to explain on the page that the desired type(s) of builds must be selected in addition to describing them in the filter expression (as shown).

Contributor guide
Research direction
Find the documentation page containing the “Filter builds using a conditional” pipeline-level setting and review the surrounding explanation and screenshot. Clarify that the selected build types—pull request, push, or tag—must also be chosen, then verify that the page makes the filtering behavior unambiguous.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100