We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The link is good, but it points to a stale branch. Example PR here: disneystreaming/alloy#84
This is because we use a hardcoded master and so if the branch still exist on the repo, the url is valid and so it's displayed:
master
val maybeSegments = repoForgeType.collect { case GitHub | GitLab => List("blob", "master") case Bitbucket => List("master") case BitbucketServer => List("browse") case Gitea => List("src", "branch", "master") }
There are different solutions:
The text was updated successfully, but these errors were encountered:
I use ChatGPT (I'm still impressed to generate an example curl command on how to do this):
bitbucket: default_branch=$(curl -s https://api.bitbucket.org/2.0/repositories/${username}/${repository} | jq -r '.mainbranch.name')
default_branch=$(curl -s https://api.bitbucket.org/2.0/repositories/${username}/${repository} | jq -r '.mainbranch.name')
github: default_branch=$(curl -s https://api.github.com/repos/${username}/${repository} | jq -r '.default_branch')
default_branch=$(curl -s https://api.github.com/repos/${username}/${repository} | jq -r '.default_branch')
gitea: default_branch=$(curl -s "${gitea_host}/api/v1/repos/${username}/${repository}" | jq -r '.default_branch')
default_branch=$(curl -s "${gitea_host}/api/v1/repos/${username}/${repository}" | jq -r '.default_branch')
All 3 works without auth on public repo, I'd need to play a bit more with it for private repository / server.
Sorry, something went wrong.
No branches or pull requests
The link is good, but it points to a stale branch. Example PR here: disneystreaming/alloy#84
This is because we use a hardcoded
master
and so if the branch still exist on the repo, the url is valid and so it's displayed:There are different solutions:
The text was updated successfully, but these errors were encountered: