Skip to content

Conversation

@amtoaer
Copy link
Contributor

@amtoaer amtoaer commented Nov 5, 2025

Closes #41995

Release Notes:

  • Fixed self-hosted BitBucket URL can not be parsed

@cla-bot cla-bot bot added the cla-signed The user has signed the Contributor License Agreement label Nov 5, 2025
@maxdeviant maxdeviant changed the title git: Fix self-hosted BitBucket url can not be parsed git: Fix self-hosted BitBucket URL can not be parsed Nov 5, 2025
@amtoaer amtoaer force-pushed the fix_bitbucket_selfhosted branch from 6f9f0a7 to 549d624 Compare November 6, 2025 07:01
@lesha-co
Copy link

lesha-co commented Nov 6, 2025

Thank you for a quick reply!
I'm not sure if self-hosted BitBucket uses different URLs but it's almost right, see:

I have:

> git config --get remote.origin.url             
ssh://git@{domain}/{project}/{repo}.git

where {domain} is bitbucket.company.tld

After running "get permalink" I get:

https://{domain}/{project}/{repo}/src/{hash}/{path}#lines-4

But when visiting the desired file in web interface I have this URL:

https://{domain}/projects/{project}/repos/{repo}/browse/{path}?at={hash}#4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed The user has signed the Contributor License Agreement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Git: fails to create a permalink to the line

3 participants