![]() ![]() ![]() I want my project files to be mine until I decide otherwise. What does this mean to you? It means that unless you have a paid account with Github, your project will be stored in such a way that anyone can come along and pull your project files, assuming they find your project. Most people have heard of Github as a place to store their projects, but I tend to prefer using Bitbucket for one simple reason: Bitbucket can have private repositories for free, while Github cannot. It’s really easy to give into enthusiasm and dive into development, but if you’re not working to keep your files safe, then disaster is quite easily right around the corner. Keeping your project’s files and progress safe should be your number one concern. “But wait,” I hear some people saying, “isn’t that just for big companies and huge software? That’s way to big and complex for someone like me. Revision control software, when used correctly, tracks all changes made to all files in your project, who made those changes, when and even allows you to go back to any change on any file throughout the history of your project. It sounds complicated, I know, but it’s really pretty simple. Not just a copy on Dropbox or some such, but real, proper version control. So, this tutorial is to help people make sure they have a backup. Back up your projects! At least once a week I see something like “help, my PC crashed and my files are corrupted!” Did they have a backup? Nope. Any other commits you make to my-updates will also appear on that branch.I’ve decided to write this tutorial out of seeing this increasing need for people to back up their projects. ![]() Open Sourcetree and notice that your repository has Uncommitted changes.įrom the Unstaged files list, place a checkmark next to the survey.html file (and any other files with uncommitted changes).įrom the Confirm Stage? dialog, click OK.Ĭlick the Commit button at the top to commit the file.Įnter a commit message in the space provided, something like Answered questions.Ĭlick the Commit button under the message box. When you switch back to the view, you see that the file has been committed but not pushed to the Bitbucket repository.įrom Sourcetree, click the Push button to push your committed changes.įrom the dialog that appears, click OK to push your branch with the commit to Bitbucket.įrom Bitbucket, click the Source page of your repository. You should see both branches in the dropdown. Make a change to the branchįrom the repository in Sourcetree, click the Show in Finder button. Now you've got a branch in Bitbucket and it's checked out to your local system, allowing you to work on and push that separate line of code. To do so, click the Check out in Sourcetree button.įrom the Checkout Existing dialog in Sourcetree, click Checkout. If you aren't sure what to name your branch, go with something like my-updates.Īfter you create a branch, you need to check it out from your local system. You'll see that you already have one branch - your main branch.Ĭlick Create a branch in the top right corner.Įnter a Branch name and click Create. However, we're going to create one from Bitbucket for the purposes of this tutorial.Ĭlick Branches from the left navigation. Because branches aren't only a Bitbucket concept, you can create one locally. Now that your repository is all set up, next comes the fun part. If you added or modified other files, you'll see those as well.Ĥ. You should see the survey.html file you modified. Display the status of the repository with git status. Make your changes, big or small, and then save and close the file.įrom your terminal window, you should still be in the repository directory unless you've changed something. Open the survey.html file (or whatever you named it) with a text editor. Like the file mentions, you can go as crazy or as simple as you like. Now, it's your turn to makes some changes to your repository. * my-updates -> origin/my-updatesīranch 'my-updates' set up to track remote branch 'my-updates' from 'origin'.Īs you can see, you've switched to your new branch locally, allowing you to work on and push that separate line of code. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |