-
Notifications
You must be signed in to change notification settings - Fork 18
Development Setup Review
Frank Matranga edited this page Sep 16, 2019
·
1 revision
That was a lot of steps to follow to get started! Luckily, most of those are one-time things. Once you have installed everything you need to, these are the only steps you need to follow each time you sit down to work on LATE:
- Get an idea for a new feature from either the Issues page, your head, a student, anyone, etc.
- Pull from the
dev
branch to make sure you are up-to-date ($ git pull origin dev
) - Create (checkout) a new branch with a name relating to its purpose (
$ git checkout -b bugfix-issue-304
) - Run the frontend and backend server in two terminals to get LATE running locally
- Make changes to the files and test them out
- Add the files to git (
$ git add --all
) - Commit the changes with a message (
$ git commit -m "Fixed issue #303 by ..."
) - Commit as many times as you need to
- When done or close to, push the commits on the new branch to the GitHub (
$ git push origin bugfix-issue-304
) - Create a pull request for your branch once you want it to be reviewed and merged!
Remember, team, the scope of what we are working on. Our goal is to make our own lives and that of our peers easier.
LATE Stack Documentation | Learning Resources | Flowchart | LATE Discord Server Invite
Backend | Frontend | Terminology
Learn LATE
- FreeCodeCamp
- Git
- Web Basics
- HTML
- CSS [coming soon]
- JS [coming soon]
- VueJS [coming soon]
- Node [coming soon]
- MongoDB [coming soon]
How LATE Works