Github user AhyoungRyu commented on the issue:
https://github.com/apache/zeppelin/pull/2154
@guicaro Not sure how your local git repo status is now, but if you think
you can't make it back to normal status, I would recommend you to remove local
Zeppelin dir and reclone it. When the PR that you want to review is based on
another branch (in this case `branch-0.7`) not master, you can do it like this.
1. check your remote repo list and its name first
```bash
$ git remote -v
origin https://github.com/guicaro/zeppelin (fetch)
origin https://github.com/guicaro/zeppelin(push)
upstream https://github.com/apache/zeppelin.git (push)
upstream https://github.com/apache/zeppelin.git (fetch)
# in this case,
```
2. sync your local repo with `upstream`
- if you already set `upstream` with
https://github.com/apache/zeppelin.git, then sync your local git repo with
`upstream`.
```bash
$ git fetch upstream
```
- But if you didn't set `upstream` yet, you can add `upstream` to your
remote repo list like below
```bash
$ git remote add upstream https://github.com/apache/zeppelin.git
# to make sure, print your remote repo list again
$ git remote -v
# fetch upstream's latest commit history
$ git fetch upstream
```
3. then create new branch based on remote's `branch-0.7`
```bash
$ git checkout -t branch-0.7
```
4. Then run
```
$ ./dev/test_zeppelin_pr.py 2156
```
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
