jprdonnelly/freeCodeCamp
1
0
Fork 0
mirror of https://github.com/freeCodeCamp/freeCodeCamp.git synced 2026-05-09 12:00:37 -04:00
Code Issues Projects Releases Wiki Activity

fix(curriculum): typo in lecture introduction to git and github (#62383)

Browse Source
This commit is contained in:
Clarence Bakosi
2025-09-26 20:46:59 +01:00
committed by GitHub
parent 762f87442d
commit 6dbc2f72b3
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
curriculum/challenges/english/blocks/lecture-introduction-to-git-and-github/688290da3736c273009129d0.md
View File

@@ -63,7 +63,7 @@ Another option is "Squash and Merge", which takes ALL of the commits from the he
Finally, there is "Rebase and Merge", which takes all of the commits, resets them to "come after" the latest commit on the base branch, then merges the head in without a merge commit. Rebasing is a complicated topic that you will learn about in depth later, so it's okay if you do not quite understand it today.
Each open source project will choose whatever merge strategy works best. But because of these differences in behaviour, you should ALWAYS create a new branch to commit your contributions on. Never commit directly to the default `main` branch, or things will get messy when you need to bring the changes down from the original repo.
Each open source project will choose whatever merge strategy works best. But because of these differences in behavior, you should ALWAYS create a new branch to commit your contributions on. Never commit directly to the default `main` branch, or things will get messy when you need to bring the changes down from the original repo.
With all of that, you have successfully created and merged your first pull request!