Is it possible to exclude forks and personal repos from a Bitbucket Server search? I've tried a few combinations but the lack of wildcards and exclusions seems to prevent this; but I'm hoping someone knows the magic combo.
Use case: I'm using search to find and track usage of a dependency across projects that work with a fork workflow, so every project appears multiple times due to the forks. I just want to get results from the primary/upstream repos.
Hello Ben
It seems searching for repositories which have been forked was already discussed in the following feature requests:
From the resources above, the exclusion of forks from code search results was implemented in Bitbucket 4.14 version. In addition, Bitbucket 5.6 improves the way forks are searched in Bitbucket. Can you please take a look at them to see if address your question?
More information can be found at search fork discovey.
Regards
Rodrigo
Excluding forks does help reduce the noise (thanks! :)), but it doesn't exclude personal repos which are not forks. We have quite a lot of those - for context imagine excluding every spike, proof of concept and ShipIt project at Atlassian.
Any chance a flag for personal repos might get added?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Having a modifier to exclude personal repositories would be an extremely useful feature. Has this been considered further in the last 2 years?
There is nothing mentioned for the latest documentation:
https://confluence.atlassian.com/bitbucketserver/search-for-code-in-bitbucket-server-814204781.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.