Hasan Awad

@astellingwerf To be clear you are suggesting to create an issue in the Gitlab issues board for the repo if there were problems with the onboarding pr ?

@astellingwerf Could you please provide an example of a push rule that you have and expected result ? Also can you clarify "If those settings are not Renovate-ready" part more

@viceice You think we should only create an issue when pushing fails incase of a push rule ?

@viceice So to make sure I understand we should only open an issue incase of a push rule violation since this error will be constant unless the user changes according...

@astellingwerf yes I was looking into how we can determine if the push fails cause of a push rule. I see we already have a catch for `ExternalHostError` in `repository/update`...

@astellingwerf Would it be better to agree on an issue template to open incase of any external error that could be helpful to users which is not specific to a...

@astellingwerf since the fail for this will be caused by an external error what kind of documentation from renovate would be helpful or relevant to show the user ? @HonkingGoose...

I've set a bound on pagination and now I'm logging the error code instead of the message. @viceice Does it look good now ?

@viceice @rarkins Can we please decide what to do with this pr if it is still needed or it should be closed ? - Currently there is caching and pagination...

I was aiming to support `/api/v1/` which was the requirement from the issue. According to the docs there is an endpoint but its at `/api/v2`: https://help.sonatype.com/iqserver/automating/rest-apis/component-versions-rest-api---v2 @rarkins Keep this or...