-
Notifications
You must be signed in to change notification settings - Fork 14
FAQ
See below. Don't include the $
in your commands.
$ git status # make sure you dont have any uncommitted changes
$ git checkout dev
$ git pull origin dev
$ git checkout <your branch>
$ git rebase dev
$ git push origin <your branch> --force
To fix this, first make sure you are on the dev branch. Run the commands below:
$ git fetch origin dev
$ git reset --hard origin/dev
# continue with the git checkout <your branch> step above
- Navigate to the Core-v4 homepage
- Select your branch from the dropdown menu below:
- If you see
x commits behind dev
like below, you need you run the steps to update your branch above.
- A failed test case often looks like below:
- That isn't the actual error. Scroll up you'll find the real issue with the test.
You are missing a dependency. Install it with npm install && npm run server-install
.
You need to run python setup.py
to generate this file.
- Type this command
$ git rebase -i dev
- Here, a text editor (typically vim) should pop up.
Small lesson on vim: press i
to enter insert mode (normal document editing) and press esc
to enter command mode. To edit the text, press i
and use the arrow keys to navigate around and backspace to delete characters. To save your work, you need to go back to command mode by pressing esc
. Then, type :wq
to save the editor. A small cheatsheet can be found here
Change all but the top pick
keyword to s
to squash your commits. An example of this file is shown below.
- Save the file. There may or may not be merge conflicts for you to resolve. Once the conflicts are resolved and the branch is done rebasing, force push to origin.
$ git push origin <your branch> --force
Your code is bad
This is a TravisCI problem. Just click on the details
to view more details on the build. Then, click on the build
and then restart build
. Screenshots can be seen below.