Darin: Workflows, 1 about home HOT 7 OPEN

@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

from home.

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 ----

-->

from home.

I have to immediately ask for help 👍

: ) 🎓

from home.

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

from home.

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

from home.

@colevandersWands thank you soooo much

from home.

to make a checklist in GitHub

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

from home.