Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

I can not pull request from my bitbucket repository, how can i use the app password to pull my repo?

I whant to pull request from my repo and i cannot 

1 answer

0 votes
Caroline R Atlassian Team Mar 10, 2022

Hi, @Hugo Paulo, welcome to the community! 

Before we start, I would like to confirm if you are trying to run a git pull or if you want to create a Pull Request to your remote repository using an API call.

If you are trying to run a git pull using an App Password, the first thing you need to confirm is if you are using the HTTPS method (and not SSH) in your local repo. In order to check that, you can run the following command:

git remote -v

If you see the following structure, this means you are using HTTPS: 

origin https://{username}{workspaceID}/{repository_name}.git (fetch)
origin https://{username}{workspaceID}/{repository_name}.git (push)

By your description, it seems that the issue you are facing is related to the recent changes with the removal of support for Atlassian account password for operations GIT over HTTPS and API requests.

This was announced in our Blog post Deprecating Atlassian account password for Bitbucket API and Git activity and shared on multiple email communication sent to our customers in the last few months. This announcement was also included in the terminal message response for HTTPS GIT transactions.

For more details on how to resolve this issue, please refer to our community post here: 

This post provides detailed instructions users need to take to help resolve the issue. This community post also provides answers to FAQ, make sure you scroll to the bottom of the page to find the answers.

If after reading the community post you have further questions, please do reach out and we will be happy to help.

Kind regards, 

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events