source: go-gitea/gitea#9833 (comment)

"...some feedback on whether the URL is correct (like checking the response of the URL to see that it does return something that looks like a .well-known/openid-configuration) rather than blindly accepting the URL would be a big improvement in user experience."

What would you like Renovate to be able to do?

I would like Renovate to renovate the .bazelversion file, which is a file that says what Bazel version the project is using. This file is consumed by Bazelisk to fetch and run the correct Bazel version.

Did you already have any implementation ideas?

1. Check what the [latest releas

Description of the problem, including code/CLI snippet

Documentation is missing an example how to make use of project import parameters.
The Gitlab-API supports these parameters (name,file,path,overwrite)

Expected Behavior

It would be good to add an example to the documentation (if those parameters are supported)

Actual Behavior

Specifications

• python-gitlab versi

#197 took care of being able to use # at the start of a line, but I just noticed that there isn't a great user flow for editing an issue that already has markdown headings.

1. Create an issue with at least 1 heading
2. Edit the issue with lab issue edit [ID]
3. Make changes and save
4. The issue will now have its heading(s) stripped out

I'm not sure what the best course would be, but

Currently if you try to clone a repository from github and you don't have any ssh keys configured at github, you will fail to clone and get such message:

Fatal error: fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Even Permission denied (publickey). message is not shown.

@guyzmo offered to "suggest a

See scala/scala-xml#359 (comment).

Hi,
Now that we have nested group in gitlab since v9 it would be very interesting to implement it in gitlab-mirrors.
Would be super useful, as we could mirror several git repositories of a unique project to a unique sub group in a base "gitlab-mirrors" group (wow!)

Cheers

https://github.com/google/starlark-go/blob/master/doc/spec.md

It should satisfy our reproducibility needs (like jsonnet) and could be easier to write agola config files.

Like in #137 we should provide build context information.