-
Notifications
You must be signed in to change notification settings - Fork 385
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
Leveraging VS Code Source Control for GIT and GitHub #155
base: main
Are you sure you want to change the base?
Changes from all commits
aa6cef3
cd6636c
559ec19
d9fc517
762f88e
ea4aff5
bdc6675
5beca48
44ce2e8
edb9a0b
b118d1e
a5159b2
7ffb562
7875e30
4aad78f
29609fa
f533053
14a9980
a08c78b
a4a519d
4c82e1e
706d01c
11d5238
d565465
fd5dcdb
bd0f6f7
38c82a1
8284611
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
@@ -0,0 +1,77 @@ | ||||||
# Leveraging VS Code Source Control for GIT and GitHub | ||||||
|
||||||
## Module Source | ||||||
|
||||||
This workshop is based on the [Work with source control using Git in Visual Studio Code](https://docs.microsoft.com/en-us/learn/modules/work-source-control-git/) | ||||||
|
||||||
## Goals | ||||||
|
||||||
In this workshop, you will learn how to leverage VS Code source control tab to perform all tasks that can be done using git commands. | ||||||
|
||||||
| **Goal** | **Description** | | ||||||
| ------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | | ||||||
| **What will you learn** | Students will be skilled at creating using VS Code Source Control to create, rename, switch and merge branches, add, commit, and even publish to GitHub | | ||||||
| **What you'll need** | [Visual Studio Code](https://code.visualstudio.com?WT.mc_id=academic-56602-chrhar) and [Git](https://git-scm.com/) | | | ||||||
| **Slides** | [Powerpoint](./slides.pptx) | | ||||||
|
||||||
## Video walk-through | ||||||
> 🎥 Click this image to watch Rasheed walk you through the workshop in a real-life workshop | ||||||
|
||||||
Taiwrash marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
[![workshop walk-through](./images/prom.gif)](https://youtu.be/_6B7Qa6-8j4 "Leveraging VS Code Source Control for GIT and GitHub | ||||||
") | ||||||
|
||||||
|
||||||
|
||||||
## Prerequisites | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This section was already mentioned above
Suggested change
|
||||||
|
||||||
- Software | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
- [Visual Studio Code](https://code.visualstudio.com?WT.mc_id=academic-56602-chrhar) | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
- [Git](https://git-scm.com/) | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
|
||||||
## What students will learn | ||||||
|
||||||
- Understands VS Code Interface | ||||||
- Perform basic Git tasks | ||||||
- Initialize | ||||||
- Branch actions | ||||||
- Stages | ||||||
- Remote | ||||||
|
||||||
|
||||||
### Introducing VS Code | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If this is the section in which you begin practicing, I think it would be great if you included a corresponding title because it can be confused with the previous section. |
||||||
|
||||||
You will start by exploring the VS code [Getting Started in Visual Studio ](https://docs.microsoft.com/en-us/learn/modules/develop-web-apps-with-vs-code/). | ||||||
|
||||||
### Create a working directory/folder | ||||||
|
||||||
Open the folder in VS Code | ||||||
|
||||||
### Create New file and add content | ||||||
|
||||||
Add files to be tracked in the working directory and click the source control tab to initialize git | ||||||
|
||||||
### Initialize Git | ||||||
|
||||||
This will create a .git folder in your working direcory which gives git to track everything in the directory. This is done once for a single project | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
### Add Commit and Publish to the GitHub | ||||||
|
||||||
After initializizing git, and still on the source control tab will gives access to plus button to stage the files added before and after adding it by pressing the buttons. Can be committed by adding commit message and press a mark like button to commit it and another button to publish will come up to publish to either private or public repository on GitHub | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think this will help to deliver your message more effectively to more students. What do you think?😃
Suggested change
|
||||||
|
||||||
## Knowledge Check | ||||||
|
||||||
[Knowledge check](https://docs.microsoft.com/en-us/learn/modules/work-source-control-git/12-check) | ||||||
|
||||||
## Next steps | ||||||
|
||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It would be great to include a message about these next steps, what they will learn and why they should continue.Please, click here for references. |
||||||
- [VS Code official documentation on source control feature](https://code.visualstudio.com/Docs/editor/versioncontrol) | ||||||
- [A quick start created for everyone](https://taiwrash.github.io/g4-workshop/beginner-intermediate/4-git-in-vscode.html) | ||||||
- [VS Code Source Control Basics Video](https://youtu.be/i_23KUAEtUM) | ||||||
|
||||||
|
||||||
## Feedback | ||||||
|
||||||
Be sure to give [feedback about this workshop](https://forms.office.com/r/MdhJWMZthR)! | ||||||
|
||||||
## [Code of Conduct](../../CODE_OF_CONDUCT.md) |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
# Leveraging VS Code Source Control for GIT and GitHub | ||
|
||
## Workshop Source | ||
|
||
[Work with source control using Git in Visual Studio Code]([https://docs.microsoft.com/learn/modules/react-get-started/?WT.mc_id=academic-56602-chrhar](https://docs.microsoft.com/en-us/learn/modules/work-source-control-git/)) | ||
|
||
## Stage 1: Desired Results | ||
|
||
Students will be skilled at creating using VS Code Source Control to create, rename, switch and merge branches, add, commit and even publish to GitHub | ||
|
||
## Stage 2: Evidence | ||
|
||
By the end of the workshop, participants will be able to leverage VS Code source control tab to perform all tasks that can be done using git commands. | ||
|
||
## Stage 3: Learning Plan | ||
|
||
1. Introduce VS Code Interface | ||
1. Setup Working Directory as Exercise | ||
1. Create, rename and work with branches | ||
1. Initialize, add, commit and publish to GitHub | ||
1. Clone from GitHub Repository |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments about the slides:
![image](https://user-images.githubusercontent.com/107883174/206803661-d45ff310-13c8-4f42-b901-b05c311124f4.png)
- Slide # 11: My suggestion is to change these sentences (the red lined ones) with wordtune, this way can help you bring clarity to your message.it would be necessary to remove this sentence (blue highlighter). My advice is that you also use Grammarly and WordTune to review it.
![image](https://user-images.githubusercontent.com/107883174/208162969-5dcddbe9-d4b9-42c8-9941-0ac04c52adef.png)
Since it seems that each section is different, adding a title here will make it easier for the audience to understand.
![image](https://user-images.githubusercontent.com/107883174/208772478-977a2966-b645-4603-b7f9-349591fb59b0.png)