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
Commit to master branch showing in history, but not in master itself.
Hi folks,
I have a BitBucket Server v6.2.0 instance with about 5 users working on one of the repo's. We're having a situation at the moment which I can't for the life of me work out what is going on.
- One of the developers working on the master branch made a change to an existing file in the project, then committed/pushed. No problems.
- When I go to pull the latest master, his change does not appear.
- When I look at the repo on the web site, the master branch does not show his change, however when I look at History for that file, the last commit is his change.
- If I click on that commit, I can see it and diff it. Everything looks fine.
- I have tried starting a completely fresh directory and cloning the project again, no joy.
This doesn't appear to be branch-related, so I'm trying to find out what can cause a commit to appear as last in the commit history, but not appear in the master head revision? Any suggestions gratefully received.
Thanks
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.