Skip to content
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

Open
wants to merge 28 commits into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from 8 commits
Commits
Show all changes
28 commits
Select commit Hold shift + click to select a range
aa6cef3
Added workshop-designer documents
Taiwrash Aug 7, 2022
cd6636c
update designer
Taiwrash Aug 7, 2022
559ec19
Added README
Taiwrash Aug 7, 2022
d9fc517
added video link
Taiwrash Aug 7, 2022
762f88e
Added slides docx
Taiwrash Aug 7, 2022
ea4aff5
created image dir
Taiwrash Aug 7, 2022
bdc6675
Added cover photo
Taiwrash Aug 7, 2022
5beca48
Delete hel.in
Taiwrash Aug 7, 2022
44ce2e8
Update full/leveraging-vscode-source-control-for-git-and-github/READM…
Taiwrash Nov 2, 2023
edb9a0b
Update full/leveraging-vscode-source-control-for-git-and-github/READM…
Taiwrash Nov 2, 2023
b118d1e
Update full/leveraging-vscode-source-control-for-git-and-github/READM…
Taiwrash Nov 2, 2023
a5159b2
Update full/leveraging-vscode-source-control-for-git-and-github/READM…
Taiwrash Nov 2, 2023
7ffb562
Update full/leveraging-vscode-source-control-for-git-and-github/READM…
Taiwrash Nov 2, 2023
7875e30
Update full/leveraging-vscode-source-control-for-git-and-github/READM…
Taiwrash Nov 2, 2023
4aad78f
Update full/leveraging-vscode-source-control-for-git-and-github/READM…
Taiwrash Nov 2, 2023
29609fa
Delete full/leveraging-vscode-source-control-for-git-and-github/slide…
Taiwrash Nov 2, 2023
f533053
update slides
Taiwrash Nov 2, 2023
14a9980
added promo
Taiwrash Nov 2, 2023
a08c78b
Update README.md
Taiwrash Nov 2, 2023
a4a519d
Update README.md
Taiwrash Nov 2, 2023
4c82e1e
added gif
Taiwrash Nov 2, 2023
706d01c
Delete full/leveraging-vscode-source-control-for-git-and-github/image…
Taiwrash Nov 2, 2023
11d5238
Delete full/leveraging-vscode-source-control-for-git-and-github/image…
Taiwrash Nov 2, 2023
d565465
Update README.md
Taiwrash Nov 2, 2023
fd5dcdb
Update README.md
Taiwrash Nov 2, 2023
bd0f6f7
Update full/leveraging-vscode-source-control-for-git-and-github/works…
Taiwrash Nov 24, 2023
38c82a1
Update full/leveraging-vscode-source-control-for-git-and-github/READM…
Taiwrash Nov 24, 2023
8284611
Update full/leveraging-vscode-source-control-for-git-and-github/READM…
Taiwrash Nov 24, 2023
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
76 changes: 76 additions & 0 deletions full/leveraging-vscode-source-control-for-git-and-github/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,76 @@
# 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. Congratulations to those who hates memorising commands ):.
Taiwrash marked this conversation as resolved.
Show resolved Hide resolved

| **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 |
Taiwrash marked this conversation as resolved.
Show resolved Hide resolved
| **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) |
Copy link
Contributor

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:

  • Slide # 2: needs to be removed because it's from a different workshop and it can confuse students.

image

  • slide # 6 : suggestion on your notes, this could be said in a friendlier way, I recommed that you use WordTune to improve your message.

image

  • Slide # 9 : it would be better if it's not included in the slides, so this can help to create a more inclusive and friendly environment to everyone.

image

- 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.

image

  • about your notes on slide 12: i think this sentence looks pretty similar to the explanation you have on slide 13

image

image

  • notes on slide 15: I recommend you use Wordtune, it will greatly enhance the clarity of your messages.

image

  • about slide 17: there is a word missing in the second sentence and I suggest to use Wordtune or grammarly to help you 😄

image

  • about slide 18: grammar here, you can see if you copy/paste your text on a Word file. Also, Grammarly can help you too 😄

image

  • about slide 19: this sentence is a bit confusing 👀

image

  • about slide 20: it would be better to remove the sentences that are in the yellow highlighter.

image

  • about slide 29: I recommend you use Wordtune, it will greatly enhance the clarity of your messages.

image

  • about slide 30: If you would like this link to be included on the slides (yellow highlighter)

image

it would be necessary to remove this sentence (blue highlighter). My advice is that you also use Grammarly and WordTune to review it.
image

Since it seems that each section is different, adding a title here will make it easier for the audience to understand.
image

  • about slide 31: i believe it would be better to change "shout out!" to "feedback" 😄

image


## Video walk-through

Taiwrash marked this conversation as resolved.
Show resolved Hide resolved
[![workshop walk-through](./images/promo.png)](https://youtu.be/_6B7Qa6-8j4 "workshop walk-through")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Super! I think including a gif would be awesome - it's easy for ambassadors to know that this is a video rather than an image. Please, click here for references.

When the requested changes have been made to your presentation (slides), please update your video. I suggest that it should be a 5-10 minute video that guides the audience (students ambassadors) to your workshop, what they will learn and how they can use it.

Suggested change
[![workshop walk-through](./images/promo.png)](https://youtu.be/_6B7Qa6-8j4 "workshop walk-through")
[![workshop walk-through](./images/promo.png)](https://youtu.be/_6B7Qa6-8j4 "workshop walk-through")

> 🎥 Click this image to watch Rasheed walk you through the workshop in real life workshop
Taiwrash marked this conversation as resolved.
Show resolved Hide resolved



## Prerequisites
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This section was already mentioned above

Suggested change
## Prerequisites


- Software
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Software

- [Visual Studio Code](https://code.visualstudio.com?WT.mc_id=academic-56602-chrhar)
Copy link
Contributor

Choose a reason for hiding this comment

The 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)

- [Git](https://git-scm.com/)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- [Git](https://git-scm.com/)



## What students will learn

- Understands VS Code Interface
- Perform basic Git tasks
- Initialize
- Branch actions
- Stages
- Remote


### Introducing VS Code
Copy link
Contributor

Choose a reason for hiding this comment

The 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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
This will create a .git folder in your working directory which gives git to track everything in the directory. This is done once for a single project.


### 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
Copy link
Contributor

Choose a reason for hiding this comment

The 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
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
As soon as git is initialized, and still on the source control tab, it will provide a plus button for staging the files and added before and after adding them by clicking the buttons. A commit message can be added and a mark like button can be pressed to commit it, then another button will appear to publish to either a private or public repository on GitHub.


## Quiz or Code Challenge
Taiwrash marked this conversation as resolved.
Show resolved Hide resolved

[Knowledge check](https://docs.microsoft.com/en-us/learn/modules/work-source-control-git/12-check)

## Next steps

Copy link
Contributor

Choose a reason for hiding this comment

The 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)
Taiwrash marked this conversation as resolved.
Show resolved Hide resolved
[A quick start created for everyone](https://taiwrash.github.io/g4-workshop/beginner-intermediate/4-git-in-vscode.html)
Taiwrash marked this conversation as resolved.
Show resolved Hide resolved
[VS Code Source Control Basics Video](https://youtu.be/i_23KUAEtUM)
Taiwrash marked this conversation as resolved.
Show resolved Hide resolved


## Feedback

Be sure to give [feedback about this workshop](https://forms.office.com/r/MdhJWMZthR)!

[Code of Conduct](../../CODE_OF_CONDUCT.md)
Taiwrash marked this conversation as resolved.
Show resolved Hide resolved
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
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. Congratulations to those who hates memorising commands ):
Taiwrash marked this conversation as resolved.
Show resolved Hide resolved

## 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