forked from freeCodeCamp/freeCodeCamp
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(curriculum): add english block 6.1 challenges (freeCodeCamp#53238)
Co-authored-by: Sem Bauke <[email protected]> Co-authored-by: Tom <[email protected]>
- Loading branch information
1 parent
839ce93
commit 2ef5a82
Showing
65 changed files
with
3,226 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4 changes: 2 additions & 2 deletions
4
...leshoot-on-github/dialogue-placeholder.md → ...oot-on-github/655c131291cbcb8febf21e64.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
40 changes: 40 additions & 0 deletions
40
...learn-how-to-help-a-coworker-troubleshoot-on-github/656b732c8110ff8936f016de.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
--- | ||
id: 656b732c8110ff8936f016de | ||
title: Task 1 | ||
challengeType: 22 | ||
dashedName: task-1 | ||
audioPath: curriculum/js-music-player/We-Are-Going-to-Make-it.mp3 | ||
|
||
--- | ||
<!-- | ||
AUDIO REFERENCE: | ||
Bob: Hey, Sarah. I was checking the _ we worked on yesterday when I saw a problem. | ||
--> | ||
|
||
# --description-- | ||
|
||
In software development, a `branch` is like a separate line of development. Think of it as a way to work on different versions of a project at the same time. | ||
|
||
For instance, one `branch` can be for new features, while another is for fixing bugs. | ||
|
||
# --fillInTheBlank-- | ||
|
||
## --sentence-- | ||
|
||
`Hey, Sarah. I was checking the _ we worked on _ when I saw a problem.` | ||
|
||
## --blanks-- | ||
|
||
`branch` | ||
|
||
### --feedback-- | ||
|
||
A version of the project where specific changes are made. | ||
|
||
--- | ||
|
||
`yesterday` | ||
|
||
### --feedback-- | ||
|
||
The day before today. |
32 changes: 32 additions & 0 deletions
32
...learn-how-to-help-a-coworker-troubleshoot-on-github/656b74ab2a075f8a05c66f41.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
--- | ||
id: 656b74ab2a075f8a05c66f41 | ||
title: Task 2 | ||
challengeType: 22 | ||
dashedName: task-2 | ||
audioPath: curriculum/js-music-player/We-Are-Going-to-Make-it.mp3 | ||
--- | ||
|
||
<!-- | ||
AUDIO REFERENCE: | ||
Bob: Hey, Sarah. I was checking the branch we worked on yesterday when I saw a problem. I think we should _ an issue on GitHub. | ||
--> | ||
|
||
# --description-- | ||
|
||
In the context of software development, to `open an issue` on platforms like GitHub means to create a report about a problem or a request for enhancement in a project. | ||
|
||
It's like telling the team, "Here's something we need to look at or fix." | ||
|
||
# --fillInTheBlank-- | ||
|
||
## --sentence-- | ||
|
||
`I think we should _ an issue on GitHub.` | ||
|
||
## --blanks-- | ||
|
||
`open` | ||
|
||
### --feedback-- | ||
|
||
To `open an issue` means to start a report or discussion about a specific problem. |
30 changes: 30 additions & 0 deletions
30
...learn-how-to-help-a-coworker-troubleshoot-on-github/656b757d8294618a5eefd710.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
--- | ||
id: 656b757d8294618a5eefd710 | ||
title: Task 3 | ||
challengeType: 22 | ||
dashedName: task-3 | ||
audioPath: curriculum/js-music-player/We-Are-Going-to-Make-it.mp3 | ||
--- | ||
|
||
<!-- | ||
AUDIO REFERENCE: | ||
Bob: Hey, Sarah. I was checking the branch we worked on yesterday when I saw a problem. I think we should open an _ on GitHub. | ||
--> | ||
|
||
# --description-- | ||
|
||
An `issue` on platforms like GitHub is a way to track tasks, enhancements, or bugs in a project. It's used to discuss and manage specific problems or ideas. For example, if there's a bug in the software, you can open an `issue` to describe and discuss how to fix it. | ||
|
||
# --fillInTheBlank-- | ||
|
||
## --sentence-- | ||
|
||
`I think we should open an _ on GitHub.` | ||
|
||
## --blanks-- | ||
|
||
`issue` | ||
|
||
### --feedback-- | ||
|
||
Refers to a report or discussion point in a project, such as a bug or a new feature idea. |
Oops, something went wrong.