> **❗Note:** If you are not familiar with the concept of repo, PR (pull request), fork and branch, start by looking at the official GitHub documentation on the subject:
5. Start modifying the code, and when you finish a part, commit the changes.
Example of commits:
- commit1: Created the frontend
- commit2: Fixed a bug in variable export
- commit3: Removed unnecessary comments and added translation support
- and so on...
## Testing
While testing the code, if you're working with the frontend, it might be frustrating to run `npm run frontend` and `npm run backend` every time. Instead, use `npm run frontend:dev` to see real-time changes on port 3090 (really!).
> Note: You must run `npm run frontend` once before you can use `npm run frontend:dev`
### How?
-`git add *` adds all files to be committed.
-`git commit -m "name-of-your-commit"` creates a commit.
-`git push` uploads the changes.
Before doing all this, I recommend using GitHub Desktop to see what you've changed.
If `git commit` fails due to ESLint errors, read the error message and understand what's wrong. It could be an unused variable or other issues.
### Possible Various Problems
If you have the main branch with many commits and don't know what to do, follow this simple guide:
⚠️ Please do this only when you have no active PRs or when you're not working on the project:
1. Do a pull origin and in the terminal write `git log` to identify how many commits you are behind.
2. Use `git rebase -i HEAD~2`, where 2 represents the number of commits you need to go back. If you need to go back 100 commits, use `git rebase -i HEAD~100`.
3. In the editor, change the "pick" for the two commits to "drop," save with "esc," then type `:wq` and press "Enter."
