|
How do people do code review in a svn system? Mailing patches around seems terrible, especially if you are doing continuous integration. My last project we were using RTC (Rational something something) which I found very confusing in the big picture but did have a very clear concept of change sets that were tied to a work item and needed to be reviewed before being committed.
|
#
¿
Feb 16, 2016 14:03
|
|
|
|
| # ¿ May 14, 2024 15:05 |
|
|
As a git novice, I really do love the command line interface. It tends to have great little helpful messages that would otherwise require Googling.
|
|
#
¿
Aug 4, 2016 23:35
|
|
|
apseudonym posted:You can rewrite any version control system's history. As an end user?
|
|
#
¿
Sep 24, 2016 13:21
|
|
|
What kind of git hooks do people find useful? We have two pre commit hooks: one to prevent committing focused jasmine JavaScript tests (focused means it will only run that test when you run the entire suite) and one to prevent someone checking in our database scheme name (because it differs between environments and should come from a setting.) smackfu fucked around with this message at 14:08 on Jan 31, 2017 |
|
#
¿
Jan 31, 2017 13:52
|
|
|
So, I understand in theory that git is decentralized version control. But practically, if our git server is down, how do I share a commit or branch with someone else on my team?
|
|
#
¿
May 15, 2017 12:48
|
|
|
How bad is it to push a large unchanging binary into git? Like a 1 gb database image. I know it's not meant for it but it's our easiest way to share files.
|
|
#
¿
Sep 17, 2017 00:11
|
|
|
What does Git LFS look like if someone doesn’t have the LFS client? Do they just get stub files instead of the binaries? Second question: Is LFS worth using if we need to store a single 500 MB file that never changes? Or should we just put in normal git?
|
|
#
¿
Feb 4, 2018 19:56
|
|
|
Is there a git one-liner to rebase and squash all the outstanding commits? Currently I do an interactive rebase and then mark all the lines except the first as squash or fixup, but that is a bit tedious.
|
|
#
¿
Apr 19, 2018 13:53
|
|
|
Cool, didn’t know about that. So in theory instead of: git commit -m wip I can do something like: git commit —fixup head And then the squash rebase will be automatic, eventually.
|
|
#
¿
Apr 20, 2018 12:20
|
|
|
Also, the non-hard reset is an under-appreciated tool. Changes the HEAD pointer and nothing else. Useful when you just want to commit your changes and don’t care about any of the specific commits you have locally.
|
|
#
¿
Dec 3, 2020 23:41
|
|
|
Maybe lock down force pushes at least? Still annoying but if people are pushing junk commits already shouldn’t be that much friction.
|
|
#
¿
Jun 5, 2023 13:08
|
|
|
Keep in mind that git hooks are client side so don’t enforce any real restrictions.
|
|
#
¿
Jun 29, 2023 13:19
|
|
|
I think he means type “git status” on the command line.
|
|
#
¿
Oct 10, 2023 23:20
|
|
|
Did CVS and SVN actually need a server like git, or could they just work with a shared network drive?
|
|
#
¿
Oct 12, 2023 00:57
|
|
|
|
| # ¿ May 14, 2024 15:05 |
|
|
necrotic posted:A shared drive in the context of CVS/SVN isn’t exactly much different than a central server. You still have a central server: it’s just for raw files instead of the SVN protocol. This was probably in the early 2000s when I was using it at work so shared windows drives were easy and already existed and running a dedicated server was a big deal.
|
|
#
¿
Oct 12, 2023 02:34
|
|