Closed slimsag closed 5 years ago
Confirmed this also happens with GitHub repositories added via the same repos
field (in a different external service, of course). The behavior is weirder there:
Uhg, it turns out this isn't an issue but is just confusing syntax on our part.
fork:no
excludes forksfork:yes
includes forks (and all other repositories)fork:only
only includes forksI guess that makes sense in retrospect. Not sure we can do anything to improve this, I should've read the docs. Closing.
Repositories added via the
repos
field incorrectly show up as both forks and not forks in search when using thefork:yes
andfork:no
filters.With the following Bitbucket Server external service configuration:
It is unclear to me yet whether or not this only affects repositories added via explicit selection in the
repos
field or not (I haven't tested) and whether or not the bug is in search or repo-updater somewhere.