The point is that spending some time working through some non-trivial use cases of git or svn or spending some structured time actually being taught to debug, what to actually do with a dump file, or to use git/svn/etc to fork and merge in a structured teaching environment is useful.
There's nothing in there that justifies making a class of it. If it's not part of a foundation class on developing software, there's a bigger problem that needs solving.
The goal is not to teach them to use the tool feature by feature but what the tools are capable of and that's valuable.
That I agree with.
Make it 1 credit. Like you said they don't need to spend a LOT of time on it, but spending SOME time on it, in a structured teaching environment is invaluable.
No, make it part of a class on building software. The best way to learn something is by doing it, and it's a complete waste of time to make a class on it because it's part of development. Making it a separate class is the height of idiocy... it justifies the pure idiocy of HR filtering out people who've done lots and lots of programming and software engineering, yet haven't shelled out their own bux for Visual Studio because they were using open source tools instead.
Nobody can learn to use a debugger or source control system effectively from never having seen one before to competent in 15-20 minutes.
They might learn enough to get a programming assignment done, but they won't touch the surface of what it can do.
I'd argue that showing someone how to use a debugger is best done when teaching them how to program. If you're showing someone how to use a debugger in a class that isn't a programming class, you're wasting their time, because at that point all you're doing is showing them the features of the debugger and creating extra busy work in the form of pointless homework assignments.
While that's standard operating practice in most colleges because they want to beat the idea of work/life balance out of students' heads so that they'll be good little mindless drones after they graduate, it's a symptom of systemic idiocy that should be rooted out and destroyed.
Rather than fixing the symptoms of a crappy education system with extra stupidity, fix the systemic problem: revamp the programming curriculum so that it's geared toward having students work through the process of analyzing requirements, designing solutions, and implementing them as part of a team with version control, profiles, and debuggers, and get them trained to deal with real life. A class on "here's how you use an IDE" will never accomplish anything of value beyond an asinine resume pad. Work the tools into the programming classes where they belong.