| Level Navigation: 1 | 2 | 3 | Current Level: 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 |
Initialize version control and push your project to GitHub.
git init)git add .)chore: initial project setupgit status - you should see “On branch main” and “nothing to commit, working tree clean”git log --oneline - you should see your commit message like “chore: initial project setup”secret-variables.js is NOT on GitHub:
secret-variables.js listed.gitignore file includes secret-variables.jsYou might be wondering why we use prefixes like chore: or feature: at the start of commit messages. These are part of a convention called Conventional Commits that helps organize and categorize your changes:
chore: - For maintenance tasks, setup, or non-functional changes (like adding files, updating dependencies, or initial project setup)feature: - For new functionality or features you’re adding to your projectfix: - For bug fixes or correctionsdocs: - For documentation changesstyle: - For formatting, styling, or code style changesrefactor: - For code restructuring without changing functionalityUsing these prefixes makes it easier to:
In this level, we use chore: because we’re doing initial project setup - creating the foundation without adding new features yet.
Next: Level 5 - Overall Project Check
| Level Navigation: 1 | 2 | 3 | Current Level: 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 |