Xin Lou : Work Flows : 2 Weeks

[XinGITLou]

The learning objective is in your module repo

Local development without git:

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

Local development with git:

• [ ] Initialize a new git repository with git init
• [x] stage changes using git add
• [x] check what is staged with git status
• [x] commit changes using git commit -m
• [x] display your repository's git history using git log
• [x] create a new branch using git branch
• [x] check out a branch using git checkout
• [x] create a new branch and check it out using git checkout -b
• [x] 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
• [x] create a new repo
• [x] clone a remote repository to your computer
• [x] using git pull and git push
• [x] make a PR

Remote Collaboration:

• [x] add collaborators
• [x] check a PR before merging it to the master or main
• [x] create issues
• [x] create a project board
• [x] link `PR to its issue
• [x] assign someone to review your PR
• [x] 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 check in

I need help with :

Nothing yet

What went well:

I was able to practice on git commands and work with other people collaboratively.

What went less well：

Accidentally pushed main branch.

Lessons Learned:

need to pay more attention to details

Sunday prepare work:

I did some preview on Sunday's class and reviewed what we have learned so far.

Learning Objectives

Using git commands to work in group project.

Week 2 Check-in

I Need Help With:

Better and more effective communication with the group

What went well?

I was able to have a better understanding how programmers work collaborativelty.

What went less well?

Need to double check branch before pushing any code.

Lessons Learned

1. How to create a issue and group project.
2. How issues and project, PR work in a group project.

Sunday Preparation

Learning Agile development online before Sunday class

Week 3 Check-in

I Need Help With:

Nothing yet.

What went well?

Team communication, i have better understanding of how agile development works.

What went less well?

Team members' skill level differentiates, though we managed to pull it through.

Lessons Learned

Communication is the key to a successful project.

Sunday Prep Work

I did some preview on Sunday's subject.

Week 4 Check-in

I Need Help With:

Nothing yet.

What went well?

Learned more about HTML and CSS

What went less well?

There are few bugs (css styling order) in the project.

Lessons Learned

I need to spend more time practicing CSS.

Sunday Prep Work

Looked through materials for Sunday class. Inspected HYF website for the next project.

Week 5 Check-in

I Need Help With:

Nothing yet.

What went well?

Managed to do the html and css part of hyf without copying and pasting

What went less well?

There are a few bugs in the website

Lessons Learned

I commented all the bugs and places I have question

Sunday Prepare

I went through different method to do responsive website such as media query, css grid and flex box

[samirm00]

@XinGITLou You already have a check-in issue , why did create a new one ?

[XinGITLou]

Sorry , thought the first one was closed

[samirm00]

@XinGITLou That is up to you and your team to find a good way to communicate. 1- why didn't you post the learning objective list at the top of your issue ?

[samirm00]

Sorry , thought the first one was closed

check-in never closed