bf-frontend-class-2023 / home Goto Github PK

my fork of module repository

Learning Objectives

Study checklist

Local development without git:

• open a new terminal window
• using cd
• using ls
• using cat
• using mkdir
• using touch
• can write a document in Markdown with no syntax mistakes
• Opening the VSCode terminal
• Deleting a file
• Deleting a folder
• Previewing a Markdown File
• Formatting a Markdown document
• using npm install
• use npm run format
• use npm run format:check
• use npm run lint:ls
• use npm run lint:md

Local development with git:

• Initialize a new git repository with git init
• stage changes using git add
• check what is staged with git status
• commit changes using git commit -m
• display your repository's git history using git log
• create a new branch using git branch
• check out a branch using git checkout
• create a new branch and check it out using git checkout -b
• merge changes from one branch to another using git merge
• return to a previous version of your project with git log and git checkout
• .gitignore: You can use a .gitignore file to describe which files you don't want to be included in your git

Local/Remote development:

• GitHub SSH Key
• create a new repo
• clone a remote repository to your computer
• using git pull and git push
• make a PR

Remote Collaboration:

• add collaborators
• check a PR before merging it to the master or main
• create issues
• create a project board
• link `PR to its issue
• assign someone to review your PR
• fix merge conflict.

Open Source Development:

• look to an open source project and find issues, and decide if you can help them.
• join open source project issue conversation
• create a help issue if you need help
• create a fork of an open-source project

Week 1

I Need Help With:

As of now everything is good.

What went well?

Last 4 days were went well and know about how to create the individual and group project.

What went less well?

Lessons Learned

1. How to Create Issue
2. How to Install NPM
3. How to Run Checklist
4. How to Commit and push our project
5. How to Merge

• repo
• I added a coach as a collaborator
• I wrote my markdown(README.md) locally on a new branch
• I pulled and merged main into my branch before pushing
• I pushed my branch to my repo and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR

• repo
• I added a coach as a collaborator
• I wrote my markdown(README.md) locally on a new branch
• I pulled and merged main into my branch before pushing
• I pushed my branch to my repo and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR

Roll Call!

Leave a comment with these two things:

1. A summary of your study using only emojis
2. Something you'd like to share, anything goes! (within respect)

emoji cheat sheet

Learning Objectives

Study checklist

Local development without git:

• open a new terminal window
• using cd
• using ls
• using cat
• using mkdir
• using touch
• can write a document in Markdown with no syntax mistakes
• Opening the VSCode terminal
• Deleting a file
• Deleting a folder
• Previewing a Markdown File
• Formatting a Markdown document
• using npm install
• use npm run format
• use npm run format:check
• use npm run lint:ls
• use npm run lint:md

Local development with git:

• Initialize a new git repository with git init
• stage changes using git add
• check what is staged with git status
• commit changes using git commit -m
• display your repository's git history using git log
• create a new branch using git branch
• check out a branch using git checkout
• create a new branch and check it out using git checkout -b
• merge changes from one branch to another using git merge
• return to a previous version of your project with git log and git checkout
• .gitignore: You can use a .gitignore file to describe which files you don't want to be included in your git

Local/Remote development:

• GitHub SSH Key
• create a new repo
• clone a remote repository to your computer
• using git pull and git push
• make a PR

Remote Collaboration:

• add collaborators
• check a PR before merging it to the master or main
• create issues
• create a project board
• link `PR to its issue
• assign someone to review your PR
• fix merge conflict.

Open Source Development:

• look to an open source project and find issues, and decide if you can help them.
• join open source project issue conversation
• create a help issue if you need help
• create a fork of an open-source project

Week 1

I Need Help With:

• I would like to know how to name branches. Can you provide some guidance on this?

What went well?

• Creating Github repository
• Creating md file
• Git commands
• Formatting a Markdown document
• Work in team

What went less well?

• I got some trouble because i forgot to run npm i in main branch

Lessons Learned

• Run npm i in the main branch before creating new branches
• First need use : npm run format, npm run format:check, npm run 'spell-check , npm run lint:ls, npm run lint:md
  and then git add , git commit -m "" , git push

• repo
• I added a coach as a collaborator
• I wrote my markdown(README.md) locally on a new branch
• I pulled and merged main into my branch before pushing
• I pushed my branch to my repo and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR

my fork of module repository

Learning Objectives

Study checklist

Local development without git:

• open a new terminal window
• using cd
• using ls
• using cat
• using mkdir
• using touch
• can write a document in Markdown with no syntax mistakes
• Opening the VSCode terminal
• Deleting a file
• Deleting a folder
• Previewing a Markdown File
• Formatting a Markdown document
• using npm install
• use npm run format
• use npm run format:check
• use npm run lint:ls
• use npm run lint:md

Local development with git:

• Initialize a new git repository with git init
• stage changes using git add
• check what is staged with git status
• commit changes using git commit -m
• display your repository's git history using git log
• create a new branch using git branch
• check out a branch using git checkout
• create a new branch and check it out using git checkout -b
• merge changes from one branch to another using git merge
• return to a previous version of your project with git log and git checkout
• .gitignore: You can use a .gitignore file to describe which files you don't want to be included in your git

Local/Remote development:

• GitHub SSH Key
• create a new repo
• clone a remote repository to your computer
• using git pull and git push
• make a PR

Remote Collaboration:

• add collaborators
• check a PR before merging it to the master or main
• create issues
• create a project board
• link `PR to its issue
• assign someone to review your PR
• fix merge conflict.

Open Source Development:

• look to an open source project and find issues, and decide if you can help them.
• join open source project issue conversation
• create a help issue if you need help
• create a fork of an open-source project

Week 1

I Need Help With:

Sometimes I am stuck in GitHub, but now everything going good.

What went well?

No problem

What went less well?

At the moment everything is okay.

Lessons Learned

How to checks status in terminal
How to add changes and do commit and push
How to create a new branch and request a pull request
How to push file in github
How to switch branch in terminal
How to use visual studio code, git bash, markdown, and github

my fork of module repository

Learning Objectives

Study checklist

Local development without git:

• open a new terminal window
• using cd
• using ls
• using cat
• using mkdir
• using touch
• can write a document in Markdown with no syntax mistakes
• Opening the VSCode terminal
• Deleting a file
• Deleting a folder
• Previewing a Markdown File
• Formatting a Markdown document
• using npm install
• use npm run format
• use npm run format:check
• use npm run lint:ls
• use npm run lint:md

Local development with git:

• Initialize a new git repository with git init
• stage changes using git add
• check what is staged with git status
• commit changes using git commit -m
• display your repository's git history using git log
• create a new branch using git branch
• check out a branch using git checkout
• create a new branch and check it out using git checkout -b
• merge changes from one branch to another using git merge
• return to a previous version of your project with git log and git checkout
• .gitignore: You can use a .gitignore file to describe which files you don't want to be included in your git

Local/Remote development:

• GitHub SSH Key
• create a new repo
• clone a remote repository to your computer
• using git pull and git push
• make a PR

Remote Collaboration:

• add collaborators
• check a PR before merging it to the master or main
• create issues
• create a project board
• link `PR to its issue
• assign someone to review your PR
• fix merge conflict.

Open Source Development:

• look to an open source project and find issues, and decide if you can help them.
• join open source project issue conversation
• create a help issue if you need help
• create a fork of an open-source project

Week 1

I Need Help With:

Need more practice.

What went well?

Gated experiences with Git.
Teamwork and shares understanding of work.

What went less well?

It took a while to understand how to work with the git.

Lessons Learned

Command work, git, github.

wrote my markdown locally on a new branch

• My bio file is named exactly the same as my GitHub username
• My bio link in the class README opens to my student bio file
• I pulled and merged main into my branch before pushing
• I pushed my branch to the class repository and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR

• repo
• I added a coach as a collaborator
• I wrote my markdown(README.md) locally on a new branch
• I pulled and merged main into my branch before pushing
• I pushed my branch to my repo and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR

• repo
• I added a coach as a collaborator
• I wrote my markdown(README.md) locally on a new branch
• I pulled and merged main into my branch before pushing
• I pushed my branch to my repo and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR

• repo
• I added a coach as a collaborator
• I wrote my markdown(README.md) locally on a new branch
• I pulled and merged main into my branch before pushing
• I pushed my branch to my repo and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR

my fork of module repository

Learning Objectives

Study checklist

Local development without git:

• open a new terminal window
• using cd
• using ls
• using cat
• using mkdir
• using touch
• can write a document in Markdown with no syntax mistakes
• Opening the VSCode terminal
• Deleting a file
• Deleting a folder
• Previewing a Markdown File
• Formatting a Markdown document
• using npm install
• use npm run format
• use npm run format:check
• use npm run lint:ls
• use npm run lint:md

Local development with git:

• Initialize a new git repository with git init
• stage changes using git add
• check what is staged with git status
• commit changes using git commit -m
• display your repository's git history using git log
• create a new branch using git branch
• check out a branch using git checkout
• create a new branch and check it out using git checkout -b
• merge changes from one branch to another using git merge
• return to a previous version of your project with git log and git checkout
• .gitignore: You can use a .gitignore file to describe which files you don't want to be included in your git

Local/Remote development:

• GitHub SSH Key
• create a new repo
• clone a remote repository to your computer
• using git pull and git push
• make a PR

Remote Collaboration:

• add collaborators
• check a PR before merging it to the master or main
• create issues
• create a project board
• link `PR to its issue
• assign someone to review your PR
• fix merge conflict.

Open Source Development:

• look to an open source project and find issues, and decide if you can help them.
• join open source project issue conversation
• create a help issue if you need help
• create a fork of an open-source project

Week 1

I Need Help With:

I need help with visual code operations with git commands.

What went well?

I learned git hub login, making profile , giving git commands on visual code .

What went less well?

I found difficulty to operate terminal code and making branch .

Lessons Learned

By attending today's class I learned git command well to operate in VS code .

• I wrote my markdown locally on a new branch
• My bio file is named exactly the same as my GitHub username
• My bio link in the class README opens to my student bio file
• I pulled and merged main into my branch before pushing
• I pushed my branch to the class repository and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR
• I
  linked my PR to this issue

• I wrote my markdown locally on a new branch
• My bio file is named exactly the same as my GitHub username
• My bio link in the class README opens to my student bio file
• I pulled and merged main into my branch before pushing
• I pushed my branch to the class repository and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR
• I
  linked my PR to this issue

Group2
Project : Intro
Project leader: Zahira Bella
Members:

• Karol
• Milena
• Maria

• repo
• issues
• a nice README
• one well-named file per person
• one pull requests for each group member
  • linting checks pass
  • code review checklist is complete
  • the reviewer merged the code

• I wrote my markdown locally on a new branch
• My bio file is named exactly the same as my GitHub username
• My bio link in the class README opens to my student bio file
• I pulled and merged main into my branch before pushing
• I pushed my branch to the class repository and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR
• I
  linked my PR to this issue

• repo
• I added a coach as a collaborator
• I wrote my markdown(README.md) locally on a new branch
• I pulled and merged main into my branch before pushing
• I pushed my branch to my repo and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR

• I wrote my markdown locally on a new branch
• My bio file is named exactly the same as my GitHub username
• My bio link in the class README opens to my student bio file
• I pulled and merged main into my branch before pushing
• I pushed my branch to the class repository and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR
• I
  linked my PR to this issue

Group4
Project : Intro
Project leader: Abdul-MalikSardalov
Members:

• iradukundajp
• inna9Z
• khalidkhan1212

• repo
• issues
• a nice README
• one well-named file per person
• one pull requests for each group member
  • linting checks pass
  • code review checklist is complete
  • the reviewer merged the code

• I wrote my markdown locally on a new branch
• My bio file is named exactly the same as my GitHub username
• My bio link in the class README opens to my student bio file
• I pulled and merged main into my branch before pushing
• I pushed my branch to the class repository and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR
• I
  linked my PR to this issue

my fork of module repository

Learning Objectives

Study checklist

Local development without git:

• open a new terminal window
• using cd
• using ls
• using cat
• using mkdir
• using touch
• can write a document in Markdown with no syntax mistakes
• Opening the VSCode terminal
• Deleting a file
• Deleting a folder
• Previewing a Markdown File
• Formatting a Markdown document
• using npm install
• use npm run format
• use npm run format:check
• use npm run lint:ls
• use npm run lint:md

Local development with git:

• Initialize a new git repository with git init
• stage changes using git add
• check what is staged with git status
• commit changes using git commit -m
• display your repository's git history using git log
• create a new branch using git branch
• check out a branch using git checkout
• create a new branch and check it out using git checkout -b
• merge changes from one branch to another using git merge
• return to a previous version of your project with git log and git checkout
• .gitignore: You can use a .gitignore file to describe which files you don't want to be included in your git

Local/Remote development:

• GitHub SSH Key
• create a new repo
• clone a remote repository to your computer
• using git pull and git push
• make a PR

Remote Collaboration:

• add collaborators
• check a PR before merging it to the master or main
• create issues
• create a project board
• link `PR to its issue
• assign someone to review your PR
• fix merge conflict.

Open Source Development:

• look to an open source project and find issues, and decide if you can help them.
• join open source project issue conversation
• create a help issue if you need help
• create a fork of an open-source project

Week 1

I Need Help With:

Get clear the steps.

What went well?

use vscode

What went less well?

know the steps

Lessons Learned

markdown

my fork of module repository

Learning Objectives

Study checklist

Local development without git:

• open a new terminal window
• using cd
• using ls
• using cat
• using mkdir
• using touch
• can write a document in Markdown with no syntax mistakes
• Opening the VSCode terminal
• Deleting a file
• Deleting a folder
• Previewing a Markdown File
• Formatting a Markdown document
• using npm install
• use npm run format
• use npm run format:check
• use npm run lint:ls
• use npm run lint:md

Local development with git:

• Initialize a new git repository with git init
• stage changes using git add
• check what is staged with git status
• commit changes using git commit -m
• display your repository's git history using git log
• create a new branch using git branch
• check out a branch using git checkout
• create a new branch and check it out using git checkout -b
• merge changes from one branch to another using git merge
• return to a previous version of your project with git log and git checkout
• .gitignore: You can use a .gitignore file to describe which files you don't want to be included in your git

Local/Remote development:

• GitHub SSH Key
• create a new repo
• clone a remote repository to your computer
• using git pull and git push
• make a PR

Remote Collaboration:

• add collaborators
• check a PR before merging it to the master or main
• create issues
• create a project board
• link `PR to its issue
• assign someone to review your PR
• fix merge conflict.

Open Source Development:

• look to an open source project and find issues, and decide if you can help them.
• join open source project issue conversation
• create a help issue if you need help
• create a fork of an open-source project

Week 1

I Need Help With:

Everything is clear

What went well?

Creating repo, issues, PRs
Work with git
Work with VS studio
Work with markdown

What went less well?

Nothing

Lessons Learned

Git, Github, VSstudio, Mardown,

Group1
Project : Intro
Project leader: Fernando
Members:

• Vlad
• Preethi
• Rahwa
• Himanshi

• repo
• issues
• a nice README
• one well-named file per person
• one pull requests for each group member
  • linting checks pass
  • code review checklist is complete
  • the reviewer merged the code

my fork of module repository

Learning Objectives

Study checklist

Local development without git:

• open a new terminal window
• using cd
• using ls
• using cat
• using mkdir
• using touch
• can write a document in Markdown with no syntax mistakes
• Opening the VSCode terminal
• Deleting a file
• Deleting a folder
• Previewing a Markdown File
• Formatting a Markdown document
• using npm install
• use npm run format
• use npm run format:check
• use npm run lint:ls
• use npm run lint:md

Local development with git:

• Initialize a new git repository with git init
• stage changes using git add
• check what is staged with git status
• commit changes using git commit -m
• display your repository's git history using git log
• create a new branch using git branch
• check out a branch using git checkout
• create a new branch and check it out using git checkout -b
• merge changes from one branch to another using git merge
• return to a previous version of your project with git log and git checkout
• .gitignore: You can use a .gitignore file to describe which files you don't want to be included in your git

Local/Remote development:

• GitHub SSH Key
• create a new repo
• clone a remote repository to your computer
• using git pull and git push
• make a PR

Remote Collaboration:

• add collaborators
• check a PR before merging it to the master or main
• create issues
• create a project board
• link `PR to its issue
• assign someone to review your PR
• fix merge conflict.

Open Source Development:

• look to an open source project and find issues, and decide if you can help them.
• join open source project issue conversation
• create a help issue if you need help
• create a fork of an open-source project

Week 1

I Need Help With:

At this point I do not have any problem.

What went well?

Almost everything on this module went well.

What went less well?

To fix and merge conflicts

Lessons Learned

GitHub and markdown

• I wrote my markdown locally on a new branch
• My bio file is named exactly the same as my GitHub username
• My bio link in the class README opens to my student bio file
• I pulled and merged main into my branch before pushing
• I pushed my branch to the class repository and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR
• I
  linked my PR to this issue

• I wrote my markdown locally on a new branch
• My bio file is named exactly the same as my GitHub username
• My bio link in the class README opens to my student bio file
• I pulled and merged main into my branch before pushing
• I pushed my branch to the class repository and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR
• I
  linked my PR to this issue

• repo
• I added a coach as a collaborator
• I wrote my markdown(README.md) locally on a new branch
• I pulled and merged main into my branch before pushing
• I pushed my branch to my repo and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR

Group3
Project : Intro
Project leader: Ervin
Members:

• Iryna
• Rekhasr
• komal

• repo
• issues
• one pull requests for each group member
• a nice README
• one well-named file per person
  • linting checks pass
  • code review checklist is complete
  • the reviewer merged the code

• repo
• I added a coach as a collaborator
• I wrote my markdown(README.md) locally on a new branch
• I pulled and merged main into my branch before pushing
• I pushed my branch to my repo and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR

• repo
• I added a coach as a collaborator
• I wrote my markdown(README.md) locally on a new branch
• I pulled and merged main into my branch before pushing
• I pushed my branch to my repo and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR

my fork of module repository

Learning Objectives

Study checklist

Local development without git:

• open a new terminal window
• using cd
• using ls
• using cat
• using mkdir
• using touch
• can write a document in Markdown with no syntax mistakes
• Opening the VSCode terminal
• Deleting a file
• Deleting a folder
• Previewing a Markdown File
• Formatting a Markdown document
• using npm install
• use npm run format
• use npm run format:check
• use npm run lint:ls
• use npm run lint:md

Local development with git:

• Initialize a new git repository with git init
• stage changes using git add
• check what is staged with git status
• commit changes using git commit -m
• display your repository's git history using git log
• create a new branch using git branch
• check out a branch using git checkout
• create a new branch and check it out using git checkout -b
• merge changes from one branch to another using git merge
• return to a previous version of your project with git log and git checkout
• .gitignore: You can use a .gitignore file to describe which files you don't want to be included in your git

Local/Remote development:

• GitHub SSH Key
• create a new repo
• clone a remote repository to your computer
• using git pull and git push
• make a PR

Remote Collaboration:

• add collaborators
• check a PR before merging it to the master or main
• create issues
• create a project board
• link `PR to its issue
• assign someone to review your PR
• fix merge conflict.

Open Source Development:

• look to an open source project and find issues, and decide if you can help them.
• join open source project issue conversation
• create a help issue if you need help
• create a fork of an open-source project

Week 1

I Need Help With:

for the moment i do not need any help. i am trying to practice more and more by my self.

What went well?

every thing went well, i did not have IT background before but i am trying my best to cope up. and so far so good. Thank you for being patience with us coach.

What went less well?

Lessons Learned

VSC, github, Markdown to be continue

• I wrote my markdown locally on a new branch
• My bio file is named exactly the same as my GitHub username
• My bio link in the class README opens to my student bio file
• I pulled and merged main into my branch before pushing
• I pushed my branch to the class repository and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR
• I
  linked my PR to this issue

my fork of module repository

Learning Objectives

Study checklist

Local development without git:

• open a new terminal window
• using cd
• using ls
• using cat
• using mkdir
• using touch
• can write a document in Markdown with no syntax mistakes
• Opening the VSCode terminal
• Deleting a file
• Deleting a folder
• Previewing a Markdown File
• Formatting a Markdown document
• using npm install
• use npm run format
• use npm run format:check
• use npm run lint:ls
• use npm run lint:md

Local development with git:

• Initialize a new git repository with git init
• stage changes using git add
• check what is staged with git status
• commit changes using git commit -m
• display your repository's git history using git log
• create a new branch using git branch
• check out a branch using git checkout
• create a new branch and check it out using git checkout -b
• merge changes from one branch to another using git merge
• return to a previous version of your project with git log and git checkout
• .gitignore: You can use a .gitignore file to describe which files you don't want to be included in your git

Local/Remote development:

• GitHub SSH Key
• create a new repo
• clone a remote repository to your computer
• using git pull and git push
• make a PR

Remote Collaboration:

• add collaborators
• check a PR before merging it to the master or main
• create issues
• create a project board
• link `PR to its issue
• assign someone to review your PR
• fix merge conflict.

Open Source Development:

• look to an open source project and find issues, and decide if you can help them.
• join open source project issue conversation
• create a help issue if you need help
• create a fork of an open-source project

Week 1

I Need Help With:

in this week Everything is clear for me ,thanks for your support

What went well?

During Week 1, I was able to successfully complete the study checklist for local development without git and with git. I was able to create a new repository, clone a remote repository to my computer, make changes, commit them, and push them back to the remote repository. I also learned how to resolve merge conflicts and make a pull request. Additionally, I practiced working as a team leader with my group on a projects.

What went less well?

While working, I encountered some difficulties with formatting a Markdown document and resolving merge conflicts. However, with practice and research, I was able to overcome these challenges and learn from them.

Lessons Learned

VSC, git bash, GitHub, Markdowns

• I wrote my markdown locally on a new branch
• My bio file is named exactly the same as my GitHub username
• My bio link in the class README opens to my student bio file
• I pulled and merged main into my branch before pushing
• I pushed my branch to the class repository and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR
• I
  linked my PR to this issue

• repo
• I added a coach as a collaborator
• I wrote my markdown(README.md) locally on a new branch
• I pulled and merged main into my branch before pushing
• I pushed my branch to my repo and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR

my fork of module repository

Learning Objectives

Study checklist

Local development without git:

• open a new terminal window
• using cd
• using ls
• using cat
• using mkdir
• using touch
• can write a document in Markdown with no syntax mistakes
• Opening the VSCode terminal
• Deleting a file
• Deleting a folder
• Previewing a Markdown File
• Formatting a Markdown document
• using npm install
• use npm run format
• use npm run format:check
• use npm run lint:ls
• use npm run lint:md

Local development with git:

• Initialize a new git repository with git init
• stage changes using git add
• check what is staged with git status
• commit changes using git commit -m
• display your repository's git history using git log
• create a new branch using git branch
• check out a branch using git checkout
• create a new branch and check it out using git checkout -b
• merge changes from one branch to another using git merge
• return to a previous version of your project with git log and git checkout
• .gitignore: You can use a .gitignore file to describe which files you don't want to be included in your git

Local/Remote development:

• GitHub SSH Key
• create a new repo
• clone a remote repository to your computer
• using git pull and git push
• make a PR

Remote Collaboration:

• add collaborators
• check a PR before merging it to the master or main
• create issues
• create a project board
• link `PR to its issue
• assign someone to review your PR
• fix merge conflict.

Open Source Development:

• look to an open source project and find issues, and decide if you can help them.
• join open source project issue conversation
• create a help issue if you need help
• create a fork of an open-source project

Week 1

I Need Help With?

Samir, can you please explain slowly because sometimes you go very fast and we can't catch up with you. but with the help of recordings it helps.

What went well?

I understood that npm run and git commands are also ok with the changes we add to the files.

What went less well?

with the commands I know but sometimes I forgot how to use them.

Lessons Learned

how to do checks
how to create a pull request and merge branches,
add changes to commit

my fork of module repository

Learning Objectives

Study checklist

Local development without git:

• open a new terminal window
• using cd
• using ls
• using cat
• using mkdir
• using touch
• can write a document in Markdown with no syntax mistakes
• Opening the VSCode terminal
• Deleting a file
• Deleting a folder
• Previewing a Markdown File
• Formatting a Markdown document
• using npm install
• use npm run format
• use npm run format:check
• use npm run lint:ls
• use npm run lint:md

Local development with git:

• Initialize a new git repository with git init
• stage changes using git add
• check what is staged with git status
• commit changes using git commit -m
• display your repository's git history using git log
• create a new branch using git branch
• check out a branch using git checkout
• create a new branch and check it out using git checkout -b
• merge changes from one branch to another using git merge
• return to a previous version of your project with git log and git checkout
• .gitignore: You can use a .gitignore file to describe which files you don't want to be included in your git

Local/Remote development:

• GitHub SSH Key
• create a new repo
• clone a remote repository to your computer
• using git pull and git push
• make a PR

Remote Collaboration:

• add collaborators
• check a PR before merging it to the master or main
• create issues
• create a project board
• link `PR to its issue
• assign someone to review your PR
• fix merge conflict.

Open Source Development:

• look to an open source project and find issues, and decide if you can help them.
• join open source project issue conversation
• create a help issue if you need help
• create a fork of an open-source project

Week 1

I Need Help With:

I understood near all so now everything is ok

What went well?

project bio

What went less well?

problems with code 'git pull' in intro project

Lessons Learned

I learned how to work with Terminal and VSCode. Now I know how to create a new branch and then merge it in GitHub, have a basic understanding of working in the group and working alone.

• I wrote my markdown locally on a new branch
• My bio file is named exactly the same as my GitHub username
• My bio link in the class README opens to my student bio file
• I pulled and merged main into my branch before pushing
• I pushed my branch to the class repository and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR
• I
  linked my PR to this issue

• I wrote my markdown locally on a new branch
• My bio file is named exactly the same as my GitHub username
• My bio link in the class README opens to my student bio file
• I pulled and merged main into my branch before pushing
• I pushed my branch to the class repository and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR
• I
  linked my PR to this issue

• I wrote my markdown locally on a new branch
• My bio file is named exactly the same as my GitHub username
• My bio link in the class README opens to my student bio file
• I pulled and merged main into my branch before pushing
• I pushed my branch to the class repository and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR
• I
  linked my PR to this issue

• repo
• I added a coach as a collaborator
• I wrote my markdown(README.md) locally on a new branch
• I pulled and merged main into my branch before pushing
• I pushed my branch to my repo and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR

Learning Objectives

Study checklist

Local development without git:

• open a new terminal window
• using cd
• using ls
• using cat
• using mkdir
• using touch
• can write a document in Markdown with no syntax mistakes
• Opening the VSCode terminal
• Deleting a file
• Deleting a folder
• Previewing a Markdown File
• Formatting a Markdown document
• using npm install
• use npm run format
• use npm run format:check
• use npm run lint:ls
• use npm run lint:md

Local development with git:

• Initialize a new git repository with git init
• stage changes using git add
• check what is staged with git status
• commit changes using git commit -m
• display your repository's git history using git log
• create a new branch using git branch
• check out a branch using git checkout
• create a new branch and check it out using git checkout -b
• merge changes from one branch to another using git merge
• return to a previous version of your project with git log and git checkout
• .gitignore: You can use a .gitignore file to describe which files you don't want to be included in your git

Local/Remote development:

• GitHub SSH Key
• create a new repo
• clone a remote repository to your computer
• using git pull and git push
• make a PR

Remote Collaboration:

• add collaborators
• check a PR before merging it to the master or main
• create issues
• create a project board
• link `PR to its issue
• assign someone to review your PR
• fix merge conflict.

Open Source Development:

• look to an open source project and find issues, and decide if you can help them.
• join open source project issue conversation
• create a help issue if you need help
• create a fork of an open-source project

Week 1

I Need Help With:

1Sometimes I run cheks in vscode and go through but when checking with github it gives an error.

What went well?

I think I learned npm run well and how to do all the checks, add new changes to files and in principle everything that we learned will not cause me any problems.

What went less well?

At the moment everything is ok.

Lessons Learned

How to do checks
How to add changes and do commit and push
How to create a new branch and request a pull request

In general, everything that we have done before does not cause problems.

• I wrote my markdown locally on a new branch
• My bio file is named exactly the same as my GitHub username
• My bio link in the class README opens to my student bio file
• I pulled and merged main into my branch before pushing
• I pushed my branch to the class repository and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR
• I
  linked my PR to this issue

• I wrote my markdown locally on a new branch
• My bio file is named exactly the same as my GitHub username
• My bio link in the class README opens to my student bio file
• I pulled and merged main into my branch before pushing
• I pushed my branch to the class repository and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR
• I
  linked my PR to this issue

• repo
• I added a coach as a collaborator
• I wrote my markdown(README.md) locally on a new branch
• I pulled and merged main into my branch before pushing
• I pushed my branch to my repo and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR

• I wrote my markdown locally on a new branch
• My bio file is named exactly the same as my GitHub username
• My bio link in the class README opens to my student bio file
• I pulled and merged main into my branch before pushing
• I pushed my branch to the class repository and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR
• I
  linked my PR to this issue

• I wrote my markdown locally on a new branch
• My bio file is named exactly the same as my GitHub username
• My bio link in the class README opens to my student bio file
• I pulled and merged main into my branch before pushing
• I pushed my branch to the class repository and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR
• I
  linked my PR to this issue

• repo
• I added a coach as a collaborator
• I wrote my markdown(README.md) locally on a new branch
• I pulled and merged main into my branch before pushing
• I pushed my branch to my repo and opened a PR
• I went through the PR checklist
• All the CI check pass
• I assigned a coach to review my PR