git/Documentation/ref-reachability-filters.txt

When combining multiple `--contains` and `--no-contains` filters, only
references that contain at least one of the `--contains` commits and
contain none of the `--no-contains` commits are shown.

When combining multiple `--merged` and `--no-merged` filters, only
references that are reachable from at least one of the `--merged`
commits and from none of the `--no-merged` commits are shown.
Doc: cover multiple contains/no-contains filters Update documentation for "git branch", "git for-each-ref" and "git tag" with notes explaining what happens when passed multiple --contains or --no-contains filters. This behavior is useful to document prior to enabling multiple merged/no-merged filters, in order to demonstrate consistent behavior between merged/no-merged and contains/no-contains filters. Signed-off-by: Aaron Lipman <alipman88@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-09-16 02:08:39 +00:00			When combining multiple `--contains` and `--no-contains` filters, only
			references that contain at least one of the `--contains` commits and
			contain none of the `--no-contains` commits are shown.
ref-filter: allow merged and no-merged filters Enable ref-filter to process multiple merged and no-merged filters, and extend functionality to git branch, git tag and git for-each-ref. This provides an easy way to check for branches that are "graduation candidates:" $ git branch --no-merged master --merged next If passed more than one merged (or more than one no-merged) filter, refs must be reachable from any one of the merged commits, and reachable from none of the no-merged commits. Signed-off-by: Aaron Lipman <alipman88@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com> 2020-09-16 02:08:40 +00:00
			When combining multiple `--merged` and `--no-merged` filters, only
			references that are reachable from at least one of the `--merged`
			commits and from none of the `--no-merged` commits are shown.