The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
×Community resources
Community resources
Community resources
- Community
- Q&A
- Sourcetree
- Questions
- Changes committed locally but not pushed
Changes committed locally but not pushed
Dear all,
It would be nice if you could tickle this problem. I logged in into a second bitbucket account ("Account B") in sourcetree and then committed my changes in the project to the original account ("Account A"). The changes were committed but not pushed. And somehow in between, I changed my password and I accidentally logged out the Account A in sourcetree.
When I realised that Account A was logged out, I logged in Account A again and logged out the Account B in bitbucket. When I opened the project, changes were committed locally, but when I tried to push it, it failed with the following errors (I successfully logged in at https://id.atlassian.com/, but it seems nothing happened?) :
git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks push -v --tags origin master:master
remote: Too many invalid password attempts. Log in at https://id.atlassian.com/ to restore access.
fatal: unable to access 'XXX': The requested URL returned error: 403
Pushing to XXX
Completed with errors, see above.
Thank you so much for your help!
Kind regards,
Steve
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.