- Install dependencies using:
npm i
- Run the application using
npm run dev
- Close the application by clicking CTRL + C then typing
Y
(for yes)
- Make sure the issue is created, note down the ID of the issue
- Go to the main branch of the project and pull all the most recent changes
git checkout main
git pull
- Create a new branch with the ID of the issue as well as a short description of the issue
git checkout -b [ID-description]
# Example
git checkout -b 22-devguide
- Then you can begin to work on the issue, you should make it a habit to regularly push your changes to your branch:
# Stage changes
git add --all
# Add a commit message
git commit -m "Some description of what was done"
# Push the changes
git push
# If this is the first time #you push changes to this #branch, you may get an error like
# "The current branch ____ has to upstream branch..."
# If you get this error, do this:
git push --set-upstream origin [Branchname]
- When you are done, push your last changes. Then merge with main and resolve conflicts
# Going to main branch
git checkout main
# Get the last changes done on main
git pull
# Go back to your branch
git checkout [Branchname]
# Merge with main
git merge main
- If you got conflicts, resolve them. Then you have to push the changes when merging with main.
git add --all
git commit -m "Merged with main"
git push
- After this is done, you can create your merge request on gitlab.
How to review merge requests:
- Read through code changes
- Check that everything works when you run the application. This can be done by:
- Go to the relevant branch using
git checkout [BRANCH-NAME]
(in the terminal in VS code) - Downloading dependencies using
npm i
- Running the application
npm run dev
- Then going through the stated steps on the part of the merge request under How to test
- If everything works as expected you can then leave the branch by doing
git checkout main
- Go to the relevant branch using
- Approve the merge request if everything seems OK