John Edelbi: Workflows , 2weeks

[johnedelbi]

[my fork of module repository]()

Learning Objectives

Priorities: 🥚, 🐣, 🐥, 🐔 (click to learn more)

There is a lot to learn in this repository. If you can't master all the material at once, that's expected! Anything you don't master now will always be waiting for you to review when you need it. These 4 emoji's will help you prioritize your study time and to measure your progress: - 🥚: Understanding this material is required, it covers the base skills you'll need for this module and the next. You do not need to finish all of them but should feel comfortable that you could with enough time. - 🐣: You have started all of these exercises and feel you could complete them all if you just had more time. It may not be easy for you but with effort you can make it through. - 🐥: You have studied the examples and started some exercises if you had time. You should have a big-picture understanding of these concepts/skills, but may not be confident completing the exercises. - 🐔: These concepts or skills are not necessary but are related to this module. If you are finished with 🥚, 🐣 and 🐥 you can use the 🐔 exercises to push yourself without getting distracted from the module's main objectives. ---

🥚 0. Local Development Without Git

Practice the foundational workflows of software development by learning to write Markdown locally on your own computer using Visual Studio Code (VSCode), the Command Line Interface (CLI), and NPM scripts to automate your code's quality (formatting, linting and spell checking).

• [x] 🥚 Folder Structures: You can explain how files and folders are stored in your computer and can find, open or create files in your computer without using the Command Line Interface.
• 🥚 Command Line Interface (CLI): In a Unix shell you can ...
  • [x] open a new terminal window
  • [x] navigate up and down directories using cd
  • [x] list the contents of a directory using ls
  • [x] view the contents of a file using cat
  • [x] create new files using touch
  • [x] create new folders using mkdir
• [x] 🥚 Markdown: You can write a document in Markdown with no syntax mistakes that renders into a well-formatted document.
• 🥚 VSCode: You can complete these workflows in VScode, and can use keyboard shortcuts to complete them all:
  • [x] Opening a repository in a new window
  • [x] Opening the VSCode terminal
  • [x] Adding a new file
  • [x] Adding a new folder
  • [x] Deleting a file
  • [x] Deleting a folder
  • [x] Previewing a Markdown File
  • [x] Formatting a Markdown document
• [x] 🥚 READMEs: You can write a README file that describes the project you are working on, why it's helpful, and how someone can use it.
• 🥚 NPM: You can use NPM commands to verify your code's quality, this includes ...
  • [x] using npm install to install a project's dependencies
  • [x] reading a package.json file to find which scripts are available for the project
  • [x] use npm run <script> to execute an npm script
• 🥚 Formatting Code: You can use Prettier to make sure all the code in your project is well-formatted:
  • [x] You can use the Prettier VSCode extension to format a document while you are writing it
  • [x] You can use npm run format to format all of the documents in your project
  • [x] You can use npm run format:check to make sure all files are well-formatted
• 🥚 Linting Folder and File Names: You can ...
  • [x] use npm run lint:ls to check all folder and file names in your project
  • [x] you can fix all linting mistakes reported by npm run lint:ls
• 🥚 Linting Code: You can ...
  • [x] use npm run lint:md to check all Markdown files in your folder for linting mistakes
  • [x] you can fix all linting mistakes reported by npm run lint:md
• 🥚 Spell Check: You can ...
  • [x] use the Code Spell Checker VSCode extension to correct spelling mistakes in your Markdown documents while you are writing
  • [x] use npm run spell-check to check the spelling in all the files of your project
  • [x] update .cspell.json to add words that should be allowed in your project
• 🥚 File and Folder Naming Conventions: You can ...
  • [x] identify and follow the naming conventions for the project you are working on.
  • [x] use npm run lint:ls to check that all files and folders follow the project's naming conventions.
  • [x] you can correct any file and folder names to make them match the project conventions.
• [x] 🐣 File Extensions: You can identify all of the languages covered at HYF and give the correct file extension. You don't need to know the languages, just recognize them.
• [x] 🐣 Touch Typing: You can write a Markdown file without looking at your keyboard to find any letters, numbers or special characters. (slowly is ok!)

🥚 1. Local Development With Git

Practice using Git to save and organize your development process. You will learn how you can use Git to go back to previous versions of your project, and to work on different changes in parallel.

• 🥚 Git: Using the CLI you can ...
  • [x] Initialize a new git repository with git init
  • [x] stage changes using git add <path>
  • [x] check what is staged with git status
  • [x] commit changes using git commit -m <message>
  • [x] display your repository's git history using git log
  • [x] create a new branch using git branch <branch-name>
  • [x] check out a branch using git checkout <branch-name>
  • [x] create a new branch and check it out using git checkout -b <branch-name>
  • [x] merge changes from one branch to another using git merge <branch-name>
  • [x] return to a previous version of your project with git log and git checkout <commit-hash>
  • [x] stash and retrieve uncommitted changes with git stash and git pop
• 🥚 .gitignore: You can use a .gitignore file to describe which files you don't want included in your git history.
• 🥚 VSCode: You can ...
  • [x] use the Git Graph extension to to visualize your repo's commit history
  • [x] use the Git Lens extension to investigate your repository's commit history
  • [x] explain how the file tree in VSCode can show you which files have uncommitted changes
• [x] 🥚 Atomic Commits: You can save your development progress using small commits with clear and helpful message.
• [x] 🐣 Feature Branches: You can organize your development process using branches. You can create a new branch for each part of your project and merge those changes to main when they are finished.

🥚 1. Local/Remote Development

Learn how you can connect your local Git repositories with a GitHub repository to add more structure to your development process and to share your projects.

• 🥚 Licenses: You can ...
  • [x] explain why it's important to include a license for your code on GitHub
  • [x] choose a license for your projects that matches how you want others to use your code
• [x] 🥚 GitHub SSH Key: You can connect your computer to your GitHub account using an SSH key, clone using the SSH link, and push/pull using your SSH connection.
• 🥚 GitHub Repositories: You can ...
  • [x] create new repository on GitHub
  • [x] write a description for your repository
  • [x] turn on GitHub Pages
  • [x] configure your repository to block pushing to main
  • [x] configure your repository to block merging to main until Continuous Integration (CI) checks have passed
• 🥚 Git Remote/Local Connection: You can ...
  • [x] clone a remote repository to your computer
  • [x] initialize a new repository locally and connect it to an empty remote repository
  • [x] push and pull changes between remote & local branches
• [x] 🥚 Pull Requests: You can create a pull request between two branches in your repository and merge changes without causing any conflicts.
• [x] 🥚 PR templates: You can use a PR template to add a checklist to all of your PRs so you are sure the code is great before merging to main.
• [x] 🥚 Continuous Integration: You can use GitHub Actions to check your code's quality before merging a pull request to the main branch.
• [x] 🐣 Local/Remote Branching Workflow: You can use a branching workflow that keeps mistakes away from the main branch and prevents conflicts from happening in GitHub. For each contribution to the project you can ...
  1. Check out a new local branch and write your code
  2. Check out main on your local machine
  3. Pull changes from remote main to local main
  4. Merge changes locally from main to your new branch
     • Fix any conflicts on your new branch before pushing!
  5. Format and lint your code
  6. Push your new local branch to your remote repository
  7. Open a Pull Request from the new branch to main
     • Go through the PR's checklist to make sure everything is correct
     • Make sure all CI checks pass!
  8. Merge your new remote branch to main
     • You can delete the branch after it's merged if you want to

[johnedelbi]

Week 1

I Need Help With:

update .cspell.json to add words that should be allowed in your project

What went well?

almost everything

What went less well?

change the file name from capital to small letters and try to push it through git

Lessons Learned

type of Licenses check status configure my repository to block pushing to main

Sunday Prep Work

I am still preparing and reading more about git and GitHub settings

[yildiztugba]

@johnedelbi you are doing well!!

I will look for that

update .cspell.json to add words that should be allowed in your project

*you don't need to link your pr to your checkin

[bermarte]

I suggest you to add a file at the time, I don't think you need to add anything other than your bio file and possibly the images you used.

[johnedelbi]

@bermarte you mean that to commit the image then commit the john bio ?

[bermarte]

@bermarte you mean that to commit the image then commit the john bio ?

Probably you used git add . by doing this you also added the file .cspell.json without realizing it. But I am not sure.

[johnedelbi]

i think that i need to add it cuz i read here in the learning objective that i need to

update .cspell.json to add words that should be allowed in your project

so next time should i push it or keep it locally?

[bermarte]

You got a point here, so strictly speaking you are correct. It's written

you can update .cspell.json to add words that should be allowed in your project.

In the sense that you have learned how to do it, you know what its function/use is. That's the list of the learning objectives for this module.

so next time should i push it or keep it locally?

I think no one else has added it, so this time you can ignore it. You can keep it locally.

[johnedelbi]

Week 2

I Need Help With:

nothing I see that everything was going well for me.

What went well?

almost everything

What went less well?

nothing

Lessons Learned

everything on workflow and I go deep on git and learn about :

git squash git rebase git cherry-pick git flow git fork and how to contribute to other projects

Sunday Prep Work

I am still preparing and reading more about Agile Development for Sunday class