Darin: Workflows, 1

[Darin-Hamouda]

you will create ONE check-in issue per module

Suggested Study:

Command Line Interface (CLI)

• [ ] relative vs. absolute paths
• [ ] The Coding Train
• [ ] Jesse Showalter
• [ ] CLI games:
  • [ ] bashcrawl - clone & play
  • [ ] Terminus - online
  • [ ] iTerm - online
• [ ] A huge cheat sheet

Visual Studio Code (VSCode):

• [ ] academind VSC tutorial
• [ ] shortcuts cheatsheet
• [ ] The Coding Train VSC Intro from VSC
• [ ] tutorial step-through
• [ ] get started
• [ ] Tips for HTML/CSS/JS Are you using Windows?
• [ ] Windows Subsystem for Linux
• [ ] WSL with VSCode
• [ ] nvm command not found

Code Quality

• [ ] formatting (all file types with prettier)
• [ ] linting
  • [ ] CSS
  • [ ] markdown
• [ ] validating HTML
• [ ] spelling checks (will do once by automation, then by hand. automated spell checks are a little annoying)

READMEs

• [ ] makeareadme.com
• [ ] bulldogjob
• [ ] meakaakka
• [ ] awesome-README-templates

Git and GitHub

Git and GitHub for Poets Learn to visualize what happens inside of Git with: learngitbranching + a Video Guide ohmygit - a git game HYF/study lab.github.com/githubtraining first day on github first week on github prepare to use github Getting Started with GitHub Creating a GitHub Repository Creating a local repo and push and much more at hackyourfuture.github.io/study lab.github.com: First Day on GitHub First Week on GitHub The Net Ninja git-it Understand how to use Atomic Commits

Collaborating on GitHub

Adding collaborators to a repository about code reviews requesting a code review Git Workflow for 2 Pull Requests Git & GitHub for Poets The Net Ninja: 11 linking PRs to Issues: reference 1, reference 2 closing Issues using keywords

GitHub Actions

For now you can think of Continuous Integration is a fancy way to say "automatically check your code before you merge". Your project repositories will all have CI scripts to help maintain a quality and consistent code base. hint: remember to enable GitHub Actions in your repository!

DevTools and the DOM

How to inspect an element inspecting-the-dom Modify the DOM. (does the source change?)

Class Recordings

HYF modules are often updated, recordings from past classes may not match this gitbook When sending a PR's with recording links please ... Indicate which class you were teaching Which week it was (if the module is more than 1 week) a helpful title or description How to inspect an element inspecting-the-dom Modify the DOM. (does the source change?)

[gelilaa]

@Darin-Hamouda could you move your check-in to a comment in this issue? The issue will be easier to understand if you have only your study plan in the main description and your check-ins + our discussions in the comments.

Let us know what you have covered in your study plan from the list of suggested-study

for reference check out this issue

[Darin-Hamouda]

Thank you 👍

my fork of the exercises repo

Check-In

I Need Help With:

What went well?

• making branches, PRs, requesting for a review.

What went less well?

at first, everything seemed fuzzy, I did not know where to start or what we have to do. after that, a few things went OK, but I'm still confused in :

• Command line , I have no idea how to do it.
• Fixing the code by Code Quality Checks (what is "linting checks pass" means?)

• Lessons Learned

  I have to immediately ask for help 👍

---- END CHECK-IN TEMPLATE ----

-->

[colevandersWands]

I have to immediately ask for help 👍

: ) 🎓

[colevandersWands]

Command line , I have no idea how to do it.

This is going to take a while before you're comfortable with it. For now there's nothing wrong with using GitHub desktop so you can stay productive (as long as you're still practicing CLI a little each day).

If you haven't yet, try the CLI games in Suggested Study and your class repo's /chill-zone. These might help you get comfortable with the terminal without the risk of deleting something important in your computer

[colevandersWands]

Fixing the code by Code Quality Checks (what is "linting checks pass" means?)

This wasn't well explained, a lot of your classmates are having trouble with this too. It's also something you'll be practicing a lot in the coming modules so no worries if you don't get it right away.

First isn't important to understand that these checks happen in two places:

• locally on your computer: when you use npm run lint:md from terminal, it will read through all of the markdown files and check for mistakes in your code. It will log all the mistakes in the console then you need to find those lines in your editor and fix the mistakes. These error messages aren't easy to understand without practice so don't hesitate to ask us how to fix them if you're blocked. (but you figured out already to ask immediately : )
• on github each time you open a pull request: this is that red x that blocks you from merging a pull request. GitHub uses the exact same script as you do locally, so if you've fixed all the linting errors before pushing your code should also pass the checks

That was a lot of words, let me know what can still be more clear.

PS. I made a mistake in the GitHub Action. you can update your group's repo with this script, that should help too. Don't worry about a PR - just copy the changes right to main

[Darin-Hamouda]

@colevandersWands thank you soooo much

[sammou00]

to make a checklist in GitHub

• [ ] task1
• [ ] task2 and you can check and uncheck by clicking on them