Please, remember the Cardinal Sin of Source Control and never commit code that doesn't compile! You will annoy people to the point of them forming a lynch mob. One of the main reasons for having source control is to share code with associates. It's well worth the occasional check on your BitBucket Repository to check that all your files are included as there is no visual clue anywhere else that they aren't.
One thing that caught me out immediately after writing this, was that the default gitignore file is set to discard any files starting with "Backup" - so you should avoid calling your projects, classes, or any files with them anything started with "Backup" if you want them under Source Control. Back to BitBucket to CheckĬlick the "Source" button on the left hand side and Presto! your project is in the Repository. It won't take long - or it shouldn't with a new project, there isn't a lot there - when it's finished you are done. Paste the URL you copied from BitBucket where prompted: "Enter the URL of an empty GIT repo" and press "Publish". This will bring up the page with "Publish to Remote Repository". In the Team Explorer pane, use the top dropdown (Probably currently showing "Changes") to select "Unsynced Commits". This will show you the PUSH command detail you need:Ĭopy that to the clipboard. When the Repository is ready, click "I have an existing project". The form that appears lets you set up the repository: you need a Name, a Description is a good idea, and the rest is up to you! :laugh: Sign in to your BitBucket account and use the top menu: "Create.Create repository". (Until you do, it won't enable the "Commit" button). Enter a commit message where it prompts you to do so. This will open the "Team Explorer" pane.Right click the Solution name, and select "Commit." from the context menu.Open the "Solution Explorer" pane, and commit your project:
Select the project type as normal, give it an appropriate name and solution name, then tick the box "Create new Git Repository" before pressing "OK". If you haven't, do this first! Getting Started Create the Project and Local Repository This also assumes you have set up an account with BitBucket and can log in and create repositories. This assumes you are using Visual Studio 2013 Community Edition, and that you have the "Microsoft Git Provider" plug-in set up and selected ("Tools.Options", "Source Control.Plug-in Selection", "Current source control plug-in" to check and select if needed.) If you don't have the plug-in installed yet, go here: MSDN So here is a simple, step-by-step guide to getting it done. it can be confusing to get set up, particularly if (like me) you don't have to do it often - so each time you try, you forgot what took you all day to work out last time.:sigh.I know I do. Next to a good solid backup system, it's the best friend a developer can have! Well, if you ignore the IDE, of course.īut. You can also view Pull Request diff with syntax language highlighting.Source Control. Pull Requests - You can view all pull requests, create a new one, Approve/Disapprove pull requests, view files, commit changes and submit comments from the pull requests.Publish - You can publish your local-only repositories to the Bitbucket server.