Not sure how to sync my private cloud Repo with the forked Repo

[Todor_Kolev]

The way I use Bitbucket:
(local)myRepo > (cloud)(private)myRepo > (cloud)(reference)myRepo

I am a new user to git, just gone through the manual but I don't remember everything.
Just to give you a better idea of my knowledge: I did manage to create and merge a Pull Request.
I am trying to do simple things, so the information out there is overwhelming for me right now. So, I hope I can ask, please!

How do I keep my private repo that's on the cloud in sync with the reference repo (on the cloud as well)?

For example, what if someone else pulls their change to the reference repo, making my private-cloud repo behind?
How would I fetch the reference repo and checkout the master (is that even the correct process?)

I only have the command line and the bitbucket site for now (would like to understand better before I use a GUI)

Any discussion, link or even a tip in the right direction will be highly appreciated.

[Daniil Penkin · Accepted solution]

Hello @Todor_Kolev,

Thanks for reaching out! I'm always happy to help.

For example, what if someone else pulls their change to the reference repo, making my private-cloud repo behind?
How would I fetch the reference repo and checkout the master (is that even the correct process?)

If your private repository is a fork of the reference repository, you'll see a Sync button in the right sidebar on the source view of that fork if your fork is behind:

You can also do this sync manually by first fetching from the upstream (reference repo) locally, then pushing to your fork repository in Bitbucket. You don't need to check out any branch (check out is about changing state of your working directory, not about repository itself). You can read more about working with multiple remotes in this Pro Git chapter.

Does this make sense? Let me know if you have any questions.

Cheers,
Daniil

[Todor_Kolev]

Hi @Daniil Penkin and thanks for responding,

Had to read your stuff 3 times but I got it in the end - cheers!

What I don't like about Atlassian products is that the menus are spread around too much and there is too much reliance on rather cryptic icons: