we are at 252 and counting!
wait, you all are using source control?
17 Likes
758, but we squashed and merged PRs for most of the season. When we started normally merging PRs that number shot up, since we try and make small commits.
2 Likes
324 for us. I’ve been promoting small, incremental changes with frequent commits. For example, we use to maybe commit once at the end of a competition, but now we’ll commit whenever we make a code change, so that we always know what code was being used for a particular match, etc.
(We might not push until the end of the day, because, you know, we’re saving the WiFi for the robots 
)
2 Likes
A surprisingly low 362 for YAGSL, I must be slacking 
3 Likes
701 in the main repo (lots of squashed merges of course): Comparing v2022.4.1...v2023.4.3 · wpilibsuite/allwpilib · GitHub
3 Likes
Surprisingly low on the main branch, only 123, but we only had 2 coders on the team. We have about 20 other branches though, each with varying commit counts. Also, many code changes done at champs didn’t have their own commit due to lack of internet access
1 Like
cough cough …32…
1 Like
you can commit without pushing. I would recommend it as it allows rollbacks incase somebody messes up.
2 Likes
258 on our 1st robot, 283 on the repo for the 2nd robot that we built mid-season. The second repo is a fork of the first, so most of the commits are the same.
Only 142 on main. Mostly because our swerve was from an off-season repo and the bulk of our arm subsystem was a single commit.
1 Like
196 for us
2 Likes
392 here…
42 commits. We squash all of our commits into one when we merge PRs. Technically should be more than that.
2 Likes
181
we have 256, 2 coders both of us have around 16k lines added and 10k deleted
1 Like
heh heh
1 Like
Might make a bit more to make some small changes, but i dont think we’ll get to 300
387…
With exactly 1 programmer who has contributed to the github, not including 7 other branches or states and champs changes (on a different branch):
