nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

origin/master doesn't move

chrisglubish

A few days ago the remote origin/master flag stopped moving along when I commit/push

Everything is working just confused why this is happening or what the implications may be. See screenshot. The "origin/master" just stays at May 6 as we keep marching along.

Accepted answers

minnsey

Excuse the stupid question, but when you pushed did it complete? Are the commits you expect showing on your host?

If there were extra commits on the host, I would expect the Branches/master to show a count of extra commits.

Does running a fetch update master?

Alternatively from the terminal you can run

>git fetch
>git log origin/master

this should show you the log for the remote

All comments

minnsey

chrisglubish

Thanks Michael,

Yes, everything has been pushing fine.

From my colleagues perspective everything is working fine. So he is getting my commits.

I've ran a fetch a bunch of times, it had no effect. I also checked the log as you suggetsed, and it shows the entries from May 6 back.

BUT, the repository in Bitbucket (the origin/master, right?) shows all of commits right up to May 13.

Screenshots attached

minnsey

OK, if git fetch doesn't seem to be picking up the new commits then it doesn't sound like its a specific Sourcetree issue.

It sounds like fetch runs but does nothing?

What happens if you clone the repo again? Is it possible your current copy is corrupted in someway

chrisglubish

Its fine if I clone. So something is indeed off with my current copy. I'll just move along, assume it was a glitch and use the clone. Thanks for your assistance.