Our developers use bitbucket to store the code for production and other development/test instances.
I have created a clone of the production instance code
When a new version is pushed into production, does the clone include those updates or do I have to clone again?
I got impatient and poked around some more. The answer is clear! I have to SYNC my clone with the production versions. It's easy, actually. When the sync occurs, there's a step where the changes are displayed and then you can accept the update.
Ah, I think I see the reason you were getting a different answer than you wanted: you're asking about forks, not clones.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah yes! Every software and discipline has its own words for the same thing.
A modern, high tech tower of Babel.
Anyway, problem solved and thanks for helping and reminding my about "forks"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do you mean getting the latest changes your developers pushed to the remote? If so, no. No need to clone again but you will have to pull from remote the get those changes locally.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Both the production and the clone are on the server/remote.
And, yes, when the developers push a change to the remote, will my clone of the production remote update as well?
In other words, is it a REAL-TIME MIRROR or a STATIC COPY?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Both Git and Mercurial treat clones as static copies, even if they're hosted on the same system. You'll need to fetch or pull to get new commits from one to the other.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.