![]() projects folder and run mkdir project-of-some-name to create a folder with the name project-of-some-name.Ģ) cd into that project folder and do git init to initialise a local git repo in there.ģ) run touch README.MD to create the README file, open it and add some basic descriptions, including links to the resources / tutorials I was implementing in that project. ![]() So my typical project setup work flow usually goes like this:ġ) Go to my. Good news: you don't need to be a shell scripting god(dess) to do it. But the steps required to set up a project, initialise a repo, and sync with Github were really annoying and repetitive, so I decided to solve the problem.īad news: this isn't going to be a big, fancy, detailed and technically sexy post. The more complete projects I had on Github, the easier it would be for recruiters. ![]() ![]() But I needed to make sure I didn't lose my hard work, and that others could see the hard work I was putting in, so every project had to go on Github. I learned by doing projects (often freeCodeCamp ones!). This post comes out of an irritation I faced personally, when I was first learning to code - setting up my local repo and syncing with Github.
0 Comments
Leave a Reply. |