Closed Crocmagnon closed 3 years ago
The fact that this works only for a single include while gitlabber supports multiple includes is an issue waiting to be opened. I want to take another shot at this, either remove the support for multiple includes (and redact from current functionality) or have this support multiple include paths by executing a query with search
per include element and merging the results.
I'd rather not deliver incomplete functionality when applying this performance optimization.
Do you know whether people tend to use it with multiple includes ? Is this a feature that's worth supporting ? That would help deciding whether to do multiple searches or removing the support for multiple includes 🙂
Also, couldn't it justâ„¢ be documented? Like "we know this currently works for only one include but we welcome pull requests to support multiple ones"?
Closing this as it degrades documented behavior
Closes #68
The current implementation doesn't add any option and piggybacks on
--include
.When there's only one include and it looks like a top level group, use the search feature of gitlab instead of blindly list all groups, subgroups and projects.