That's a good summary. This is the flow that I use when I'm working on a small project -- either solo or one other contributor. But, for a lot of client projects I'm on, we'll add another layer by including a dev branch: - Pull work from dev remote to dev local. Get the newest changes from the team. - Local: Make my own branch to code features, this branch gets pushed to remote. - Pull request to merge my new branch to dev. - The dev branch is tested on the staging server - Admin / Tech lead will merge generally merge dev to master which automatically gets pushed to the production server.

@@SelfTeachMe ok.so all members will work with dev branch. Admin will test and merge it to master on remote.

@@huyttvlog That's right.

@@SelfTeachMe what do you mean by staging server, is it like dev instance website where client can changes before moving to prod

That's a good question! ... Yes! On a staging server, you can preview the site and if you have clients, then they can also preview and make changes before going live. But, even if you don't have clients, it can still be useful to have a staging server so that you can make sure that your site looks right on the server. How many times have you heard, "it looks good on my machine?! 😂" A staging server should have the exact same settings that your production server has so that if there are any consistencies between your computer and the server, you're able to catch them before the world does.

Glad it helped

Thanks for the kind words!

I'm so glad!

Pedro // thanks for the feedback. I’d be curious if you think the same about some of my newer videos. I’ve tried to be more cognizant of the levels and mixing.

@@SelfTeachMe I def. will in the near future. This was a great video and I enjoyed the overall editing. Thank you for the content!

You bet!

That comes from Oh My Zsh. Check out this video: kzfaq.info/get/bejne/esmfgbGHssWrnIU.html

Thanks!

Sure! Even after a merge, you still have to delete the old branch. This is true for local and remote branches. Although, GitHub, will ask you after you merge a branch in if you want to delete it. // delete branch locally git branch -d localBranchName // delete branch remotely git push origin --delete remoteBranchName

@@SelfTeachMe Thanks for the answer. Well, I was actually saying that after confirming the merge, I clicked "Delete" button on the Github prompt that says "You can safely delete the branch". Doesn't it should have deleted the branch on remote?

@@kamalchoudhary8364 Yes, clicking the delete button should delete the branch on your remote. If you can still see it when you run the git commands locally, you might need to refetch your branches.

@@SelfTeachMe Yes, it worked exactly as you described. One quick tip for future readers is that you can also use "git fetch --prune". Thank you so much, Amy!

Sorry about that, I've tried to make improvements since this video was posted.

Thanks for the feedback.

@@SelfTeachMe I will the big fan ...for you. I have issue about add collaborator to the repo.. showed me the accept link in Email , and when I click to he link it take to the git and the collaborator still awaiting......how can I solve the problem.....

@@dadizalamite You're not trying to become a collaborator on the project. You either want to "Fork" the repo (button in the top right). This will put a copy of the repo on your GitHub account or click on the "Clone or download" button (green button above the repo file list). This will download a copy of the code to your computer.

@@SelfTeachMe very usefull

Totally agree! ... I think it's beneficial to know the commands so you have the vocabulary. But, I always use Tower or the built-in tools inside VS Code