-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DECIDED] Use git from VSCode, investigate if it works #82
Comments
I'd vote to only use git from VSCode. This will simplify the prereqs and teaching too 👍 |
It is good! However, what was the reason why we did not want it in November course? |
As far as I remember, this was because back then, one had to install the git plugin. where no, a user always has it. Also maybe because VSCode seems a lot more polished nowadays: for me, it used to feel clunky, now it feels smooth. |
It seems like that this issue has been decided upon, as the version control teacher agrees 👍 . I unassign Lars and remove the 'Discuss in meeting' label 👍 |
I've added this decision a bit to the prereqs. |
|
Currently, we teach how to use git from the command line, which currently takes around 4 hours (and this may not be enough, according to #126). However, the course is not about git. Instead, the course is about version control and why version control is important.
To get closer to this ideal: VS Code has a very nice git plugin built-in, where it is mostly button mashing to get the thing to work. Hardest part will be us teaching where to click :-)
What about we use that one instead?
The text was updated successfully, but these errors were encountered: