What does your team use to share code?

[feverittm]

Use GitHub and fork/push/pull the code for development. They have a great set of tutorials to help learn the process and the give each FIRST team a free private repository.

[Andrew Schreiber]

Seconding github.

They'll give FRC teams more than one private repo if you ask. I know 79 has at least 5.

[pastelpony]

Github. Though we personally use flash drives.

[RamZ]

Originally Posted by Andrew Schreiber

Seconding github.

They'll give FRC teams more than one private repo if you ask. I know 79 has at least 5.

Our GitHub Settings shows that we were given a free Bronze account, providing 10 free private repositories.

[cgmv123]

We currently use GitHub as well, but in the past we've simply done all of our robot programming on one laptop (with a second laptop serving as a backup). There are disadvantages to that, but it makes sure there's only one copy of the code.

[Adamz_]

adding another one for github, but when its very simple code we just use pastebin

[Sparkyshires]

Another for github. A bit of a learning curve to get used to it, but the features are super powerful. Also hip and new it's what all the cool kids use.

[phurley67]

One last thing about git is that it allows for access to your complete history even without internet access, which can be very helpful at most competitions -- not that we ever have to edit our code at competition :-)

[frcteam2501]

Thanks for all the help!
On our team it seems like every programmer brings their own computer to work on so we will try using Github, the problem we've been having with flash drives is that you can't easily merge codes, does Github merge codes if 2 people are working at once? (anyone have a link to a tutorial on how to use it for FRC?)

[codes02]

Yes, git (the software one uses to publish changes to github and to manage changes made to software locally) is very good at handling merges. See http://git-scm.com/book/en/v2/Git-Br...ng-and-Merging

[baumgartensam]

Originally Posted by frcteam2501

Thanks for all the help!
On our team it seems like every programmer brings their own computer to work on so we will try using Github, the problem we've been having with flash drives is that you can't easily merge codes, does Github merge codes if 2 people are working at once? (anyone have a link to a tutorial on how to use it for FRC?)

Yes, that is one of git (and therefore Github's) most powerful features. Most code that is used for FRC (java or c++) will be automatically merged very nicely.

Github is also one of the largest hosted source control products used today. It's a good skill to have (ability to use git) as you will need to use it out in the professional world.

Pull requests are one feature Github has which enable teams to do code review (aka before code enters the main code base, another person has to look over it first). This is a really good practice to get into and Github makes it very easy to do. https://help.github.com/articles/using-pull-requests/

Lastly, Github gives FRC teams a free silver organization (https://github.com/pricing). You can request it at https://github.com/edu.

[Jpatterson1710]

We use dropbox. Any programmers, or anyone who might just use the code is invited to a shared dropbox folder. If you download the dropbox program is shows up like any other folder on your device, and you can save just like normal. Everyone will have access to the newest code immediately after its saved on whatever device last worked on it.

[frcteam2501]

What happens if you have 2 programmers working on code at the same time? Does dropbox try to merge your codes? or does it just take the newest one?

[yash101]

Git is probably a really good way to keep your code, even if you are programming yourself. I have a GitHub account and it has saved me a lot of work.

Just yesterday, I had a problem, where I was pushing a small change to my repo in the sky at GitHub. I tried to remove the build folder using the command:

PHP Code:

rm -r *build 


I forgot "build" and all of a sudden, my command became:

PHP Code:

rm -r * 


Too bad so sad for the work done. It's alright though. My change was quite small. Because of that, I just cloned the repo again and redid that change.
It took me about 15 minutes to fix my large mistake.
If I didn't use GitHub, I would have lost 2 weeks of work!