This repository was archived by the owner on Apr 14, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 10
General Instructions
Roy Mosby edited this page Feb 9, 2023
·
2 revisions
Note: Setup is also covered in lesson 1.1
- In GitHub, create your own repository in GitHub with the name
react-todo - Click the "Code" button and copy the URL for your repository
- In your local development environment, open up your terminal in the location where you want your project to reside.
- Clone this repository so that the code is available on your local machine:
git clone <url>Note: replace <url> with the URL you copied in the previous step
- Navigate to the directory you just cloned in your terminal with the following command:
cd react-todo- On GitHub, merge your pull request on from the previous lesson into
main.
- In your local development environment, checkout your main branch and pull changes:
git checkout main
git pull- Create a new branch for the lesson:
git checkout -b <branch>Note: Replace <branch> with your new branch name (ex. lesson-1-1)
- Open the project directory in your code editor and begin the lesson.
- Make sure application works in browser before submission.
- Perform code cleanup:
- remove any private comments, commented-out code
- ensure formatting (indentation, spaces around brackets, etc.) is consistent
- Check the status of your local repository to double-check the changes you made:
git status- Stage the file(s) that you edited:
git add .- Check the status again and notice that the changes from before are now staged:
git status- Create a commit for the changes you made and add a message describing the changes you made:
Note: Replace <message> with your message
git commit -m "<message>"- Push your commit to the remote repository (visible in GitHub):
git push- Check the log to make sure your commit has been published:
git log --oneline
-
Go to the repo in GitHub and create a pull request.
-
Copy the link of the pull request in the browser's URL bar and keep handy for assignment submission. The structure of the link should resemble:
|username |repo name |contains "pull" in URL
https://github.com/starstudent123/ctd-react-albatross/pull/18
Note: PRs increment so the number does not represent the lesson number. The example above is the 18th PR opened on that repo.
Visual instructions to create PR
A common occurrence is that students open PRs on original class repo:
INCORRECT: wrong repo
|should not contain CTD GitHub org name
https://github.com/Code-the-Dream-School/ctd-react-albatross/pull/51
Another common mistake is submitting links that are not to a PR:
INCORRECT: wrong types of links; not PRs
https://github.com/starstudent123/ctd-react-albatross
https://github.com/starstudent123/ctd-react-albatross/tree/main/src
https://github.com/starstudent123/ctd-react-albatross/blob/main/src/App.js