I am new to bitbucket, till now I have worked on TFS ( Microsoft).In TFS user has local workspace(working directory) and simply pushes changes to Global ( remote) repository.
Here in BitBucket we commit first. And once all changes are commited ,we push all in one go.
what benefit we get having commit and then push. What if we dont have commit in bit bucket and straightway push?
The simple answer is that "it is the GIT way". Git lets you work offline and commit happens locally. You need to push only when you need your code to be in the central repo. It is not a restriction on the Bitbucket end.
You might want to read more about Git to understand the difference between the Git way and the old checkin/checkout way.
Having said that, tools like SourceTree and EGit has an option to commit and push in a single click. You can use it if you really want to.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs