You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6a149e2
Browse filesBrowse the repository at this point in the historyBrowse files
GitHub Workshop Bot
committed
Challenge 10/11: use README.md in sci-fi repo, sync all templates and docs
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/challenge-10-go-local.yml
+11-13Lines changed: 11 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ body:
11
11
12
12
**Chapters:** [Ch11: VS Code Interface](https://github.com/Community-Access/git-going-with-github/blob/main/docs/11-vscode-interface.md) | [Ch13: How Git Works](https://github.com/Community-Access/git-going-with-github/blob/main/docs/13-how-git-works.md) | [Ch14: Git in Practice](https://github.com/Community-Access/git-going-with-github/blob/main/docs/14-git-in-practice.md)
13
13
14
-
**What you will do:** Clone the learning-room to your computer, create a feature branch, make an edit, commit locally, and push to GitHub.
14
+
**What you will do:** Clone the sci-fi themes repo to your computer, create a feature branch, make an edit to the README.md file, commit locally, and push to GitHub.
15
15
16
16
### The local workflow
17
17
@@ -42,19 +42,17 @@ body:
42
42
4. Press Enter
43
43
44
44
**Step 3: Edit a file**
45
-
1. In the explorer on the left, navigate to `docs/`
46
-
2. Open any file in the `docs/` folder
47
-
3. Find a typo, improve a sentence, or add a helpful comment
48
-
4. Make a small, meaningful change (just 1-2 lines)
45
+
1. In the explorer on the left, open `README.md`
46
+
2. Add a comment, fix a typo, or improve a sentence (just 1-2 lines)
49
47
50
48
**Step 4: Commit your change**
51
49
1. Press Ctrl+Shift+G to open the Source Control panel
52
50
2. You will see your modified file listed
53
51
3. Select the **+** next to it to **Stage** the change
54
-
4. In the message field at the top, write a commit message:
55
-
```
56
-
fix: correct typo in chapter 5
57
-
```
52
+
4. In the message field at the top, write a commit message:
53
+
```
54
+
docs: improve README wording
55
+
```
58
56
5. Press Ctrl+Enter (or select the checkmark) to **Commit**
59
57
60
58
**Step 5: Push to GitHub**
@@ -70,7 +68,7 @@ body:
70
68
**Step 1: Clone the repository**
71
69
1. Open GitHub Desktop
72
70
2. Choose File > Clone Repository
73
-
3. Paste the URL: `https://github.com/Community-Access/learning-room.git`
71
+
3. Paste the URL: `https://github.com/Community-Access/vscode-sci-fi-themes.git`
74
72
4. Choose a folder location
75
73
5. Select Clone
76
74
@@ -83,13 +81,13 @@ body:
83
81
84
82
**Step 3: Edit a file**
85
83
1. Select **Show in Explorer** to open the folder
86
-
2. Navigate to `docs/`
87
-
3. Open any file and make a small improvement (fix typo, improve wording, add comment)
84
+
2. Open `README.md`
85
+
3. Add a comment, fix a typo, or improve a sentence
88
86
89
87
**Step 4: Commit your change**
90
88
1. Go back to GitHub Desktop
91
89
2. You should see your change listed
92
-
3. At the bottom-left, write a commit message: `fix: correct typo in chapter 5`
90
+
3. At the bottom-left, write a commit message: `docs: improve README wording`
<p><strong>Chapters:</strong><ahref="https://github.com/Community-Access/git-going-with-github/blob/main/docs/11-vscode-interface.md">Ch11: VS Code Interface</a> | <ahref="https://github.com/Community-Access/git-going-with-github/blob/main/docs/13-how-git-works.md">Ch13: How Git Works</a> | <ahref="https://github.com/Community-Access/git-going-with-github/blob/main/docs/14-git-in-practice.md">Ch14: Git in Practice</a></p>
798
-
<p><strong>What you will do:</strong> Clone the learning-room to your computer, create a feature branch, make an edit, commit locally, and push to GitHub.</p>
798
+
<p><strong>What you will do:</strong> Clone the sci-fi themes repo to your computer, create a feature branch, make an edit to the README.md file, commit locally, and push to GitHub.</p>
799
799
<h3id="the-local-workflow">The local workflow</h3>
800
800
<p>This is the professional Git workflow you will use for the rest of your career:</p>
801
801
<ol>
@@ -825,18 +825,16 @@ <h3 id="choose-your-tool-and-follow-the-steps">Choose your tool and follow the s
825
825
</ol>
826
826
<p><strong>Step 3: Edit a file</strong></p>
827
827
<ol>
828
-
<li>In the explorer on the left, navigate to <code>docs/</code></li>
829
-
<li>Open any file in the <code>docs/</code> folder</li>
830
-
<li>Find a typo, improve a sentence, or add a helpful comment</li>
831
-
<li>Make a small, meaningful change (just 1-2 lines)</li>
828
+
<li>In the explorer on the left, open <code>README.md</code></li>
829
+
<li>Add a comment, fix a typo, or improve a sentence (just 1-2 lines)</li>
832
830
</ol>
833
831
<p><strong>Step 4: Commit your change</strong></p>
834
832
<ol>
835
833
<li>Press Ctrl+Shift+G to open the Source Control panel</li>
836
834
<li>You will see your modified file listed</li>
837
835
<li>Select the <strong>+</strong> next to it to <strong>Stage</strong> the change</li>
838
-
<li>In the message field at the top, write a commit message:<pre><codeclass="hljs"><spanclass="hljs-attribute">fix</span>: correct typo in chapter <spanclass="hljs-number">5</span></code></pre>
839
-
</li>
836
+
<li>In the message field at the top, write a commit message:
837
+
<code>docs: improve README wording</code></li>
840
838
<li>Press Ctrl+Enter (or select the checkmark) to <strong>Commit</strong></li>
841
839
</ol>
842
840
<p><strong>Step 5: Push to GitHub</strong></p>
@@ -852,7 +850,7 @@ <h3 id="choose-your-tool-and-follow-the-steps">Choose your tool and follow the s
852
850
<ol>
853
851
<li>Open GitHub Desktop</li>
854
852
<li>Choose File > Clone Repository</li>
855
-
<li>Paste the URL: <code>https://github.com/Community-Access/learning-room.git</code></li>
853
+
<li>Paste the URL: <code>https://github.com/Community-Access/vscode-sci-fi-themes.git</code></li>
856
854
<li>Choose a folder location</li>
857
855
<li>Select Clone</li>
858
856
</ol>
@@ -867,14 +865,14 @@ <h3 id="choose-your-tool-and-follow-the-steps">Choose your tool and follow the s
867
865
<p><strong>Step 3: Edit a file</strong></p>
868
866
<ol>
869
867
<li>Select <strong>Show in Explorer</strong> to open the folder</li>
870
-
<li>Navigate to <code>docs/</code></li>
871
-
<li>Open any file and make a small improvement (fix typo, improve wording, add comment)</li>
868
+
<li>Open <code>README.md</code></li>
869
+
<li>Add a comment, fix a typo, or improve a sentence</li>
872
870
</ol>
873
871
<p><strong>Step 4: Commit your change</strong></p>
874
872
<ol>
875
873
<li>Go back to GitHub Desktop</li>
876
874
<li>You should see your change listed</li>
877
-
<li>At the bottom-left, write a commit message: <code>fix: correct typo in chapter 5</code></li>
875
+
<li>At the bottom-left, write a commit message: <code>docs: improve README wording</code></li>
878
876
<li>Select <strong>Commit to fix/YOUR-USERNAME</strong></li>
<p><strong>Step 4: Write your PR description</strong></p>
936
934
<pre><codeclass="hljs"><spanclass="hljs-comment">## What this PR does</span>
937
-
Fixes<spanclass="hljs-keyword">a</span>typo<spanclass="hljs-keyword">in</span><spanclass="hljs-keyword">the</span>chapter<spanclass="hljs-number">5</span><spanclass="hljs-built_in">file</span>that was confusing readers.
Copy file name to clipboardExpand all lines: admin/qa-bundle/learning-room/.github/ISSUE_TEMPLATE/challenge-10-go-local.yml
+11-13Lines changed: 11 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ body:
11
11
12
12
**Chapters:** [Ch11: VS Code Interface](https://github.com/Community-Access/git-going-with-github/blob/main/docs/11-vscode-interface.md) | [Ch13: How Git Works](https://github.com/Community-Access/git-going-with-github/blob/main/docs/13-how-git-works.md) | [Ch14: Git in Practice](https://github.com/Community-Access/git-going-with-github/blob/main/docs/14-git-in-practice.md)
13
13
14
-
**What you will do:** Clone the learning-room to your computer, create a feature branch, make an edit, commit locally, and push to GitHub.
14
+
**What you will do:** Clone the sci-fi themes repo to your computer, create a feature branch, make an edit to the README.md file, commit locally, and push to GitHub.
15
15
16
16
### The local workflow
17
17
@@ -42,19 +42,17 @@ body:
42
42
4. Press Enter
43
43
44
44
**Step 3: Edit a file**
45
-
1. In the explorer on the left, navigate to `docs/`
46
-
2. Open any file in the `docs/` folder
47
-
3. Find a typo, improve a sentence, or add a helpful comment
48
-
4. Make a small, meaningful change (just 1-2 lines)
45
+
1. In the explorer on the left, open `README.md`
46
+
2. Add a comment, fix a typo, or improve a sentence (just 1-2 lines)
49
47
50
48
**Step 4: Commit your change**
51
49
1. Press Ctrl+Shift+G to open the Source Control panel
52
50
2. You will see your modified file listed
53
51
3. Select the **+** next to it to **Stage** the change
54
-
4. In the message field at the top, write a commit message:
55
-
```
56
-
fix: correct typo in chapter 5
57
-
```
52
+
4. In the message field at the top, write a commit message:
53
+
```
54
+
docs: improve README wording
55
+
```
58
56
5. Press Ctrl+Enter (or select the checkmark) to **Commit**
59
57
60
58
**Step 5: Push to GitHub**
@@ -70,7 +68,7 @@ body:
70
68
**Step 1: Clone the repository**
71
69
1. Open GitHub Desktop
72
70
2. Choose File > Clone Repository
73
-
3. Paste the URL: `https://github.com/Community-Access/learning-room.git`
71
+
3. Paste the URL: `https://github.com/Community-Access/vscode-sci-fi-themes.git`
74
72
4. Choose a folder location
75
73
5. Select Clone
76
74
@@ -83,13 +81,13 @@ body:
83
81
84
82
**Step 3: Edit a file**
85
83
1. Select **Show in Explorer** to open the folder
86
-
2. Navigate to `docs/`
87
-
3. Open any file and make a small improvement (fix typo, improve wording, add comment)
84
+
2. Open `README.md`
85
+
3. Add a comment, fix a typo, or improve a sentence
88
86
89
87
**Step 4: Commit your change**
90
88
1. Go back to GitHub Desktop
91
89
2. You should see your change listed
92
-
3. At the bottom-left, write a commit message: `fix: correct typo in chapter 5`
90
+
3. At the bottom-left, write a commit message: `docs: improve README wording`
**Chapters:**[Ch11: VS Code Interface](https://github.com/Community-Access/git-going-with-github/blob/main/docs/11-vscode-interface.md) | [Ch13: How Git Works](https://github.com/Community-Access/git-going-with-github/blob/main/docs/13-how-git-works.md) | [Ch14: Git in Practice](https://github.com/Community-Access/git-going-with-github/blob/main/docs/14-git-in-practice.md)
594
594
595
-
**What you will do:** Clone the learning-room to your computer, create a feature branch, make an edit, commit locally, and push to GitHub.
595
+
**What you will do:** Clone the sci-fi themes repo to your computer, create a feature branch, make an edit to the README.md file, commit locally, and push to GitHub.
596
596
597
597
### The local workflow
598
598
@@ -623,19 +623,17 @@ This is the professional Git workflow you will use for the rest of your career:
623
623
4. Press Enter
624
624
625
625
**Step 3: Edit a file**
626
-
1. In the explorer on the left, navigate to `docs/`
627
-
2. Open any file in the `docs/` folder
628
-
3. Find a typo, improve a sentence, or add a helpful comment
629
-
4. Make a small, meaningful change (just 1-2 lines)
626
+
1. In the explorer on the left, open `README.md`
627
+
2. Add a comment, fix a typo, or improve a sentence (just 1-2 lines)
630
628
631
629
**Step 4: Commit your change**
632
630
1. Press Ctrl+Shift+G to open the Source Control panel
633
631
2. You will see your modified file listed
634
632
3. Select the **+** next to it to **Stage** the change
635
-
4. In the message field at the top, write a commit message:
636
-
```
637
-
fix: correct typo in chapter 5
638
-
```
633
+
4. In the message field at the top, write a commit message:
634
+
```
635
+
docs: improve README wording
636
+
```
639
637
5. Press Ctrl+Enter (or select the checkmark) to **Commit**
640
638
641
639
**Step 5: Push to GitHub**
@@ -651,7 +649,7 @@ This is the professional Git workflow you will use for the rest of your career:
651
649
**Step 1: Clone the repository**
652
650
1. Open GitHub Desktop
653
651
2. Choose File > Clone Repository
654
-
3. Paste the URL: `https://github.com/Community-Access/learning-room.git`
652
+
3. Paste the URL: `https://github.com/Community-Access/vscode-sci-fi-themes.git`
655
653
4. Choose a folder location
656
654
5. Select Clone
657
655
@@ -664,13 +662,13 @@ This is the professional Git workflow you will use for the rest of your career:
664
662
665
663
**Step 3: Edit a file**
666
664
1. Select **Show in Explorer** to open the folder
667
-
2.Navigate to `docs/`
668
-
3.Open any file and make a small improvement (fix typo, improve wording, add comment)
665
+
2. Open `README.md`
666
+
3. Add a comment, fix a typo, or improve a sentence
669
667
670
668
**Step 4: Commit your change**
671
669
1. Go back to GitHub Desktop
672
670
2. You should see your change listed
673
-
3. At the bottom-left, write a commit message: `fix: correct typo in chapter 5`
671
+
3. At the bottom-left, write a commit message: `docs: improve README wording`
674
672
4. Select **Commit to fix/YOUR-USERNAME**
675
673
676
674
**Step 5: Push to GitHub**
@@ -723,7 +721,7 @@ The PR creation step is the same. Git just moves you between locations.
723
721
### Step-by-step instructions
724
722
725
723
**Step 1: Check for a notification banner**
726
-
1. Go to the learning-room repository on GitHub.com
724
+
1. Go to the sci-fi themes repository on GitHub.com
727
725
2. You may see a notification banner at the top saying "Your branch had recent pushes"
728
726
3. If so, select **Compare & pull request** - this is a shortcut
729
727
4. Skip to Step 3
@@ -738,16 +736,16 @@ The PR creation step is the same. Git just moves you between locations.
738
736
**Step 3: Write your PR title**
739
737
Write a clear, specific title about what you changed:
740
738
```
741
-
Fix typo in chapter 5 documentation
739
+
docs: improve README wording
742
740
```
743
741
744
742
**Step 4: Write your PR description**
745
743
```
746
744
## What this PR does
747
-
Fixes a typo in the chapter 5 file that was confusing readers.
745
+
Improves the README by clarifying the instructions and fixing a typo.
748
746
749
747
## Why
750
-
Clear documentation helps new developers learn faster.
748
+
Clear documentation helps new developers and theme users understand the project.
0 commit comments