Cannot find a merge base about git-appraise-eclipse HOT 4 OPEN

Thanks for the further clarifications; I think I understand the issue now.

To fix this, I think we need to extend the plugin to support arbitrary target refs and not just 'refs/heads/master'.

The command line tool (git-appraise) does support arbitrary target refs, but we didn't include that level of flexibility in the eclipse plugin. There's nothing intrinsically hard about that... it just got overlooked.

So, what you will want (once we add the necessary support for specifying the target ref) is to:

1. Checkout your feature branch (e.g. "feature/my-new-feature").
2. Make your changes there and commit.
3. Create a new review task specifying the "develop" branch as the target.

Until we have that, there are a couple of workarounds you could try:

1. Use the 'git-appraise' command line tool to actually create the review.
2. Create a local 'master' branch that is set up to track the remote 'develop' branch.

from git-appraise-eclipse.

Thanks for reaching out. I have a couple of follow up questions:

1. To clarify, the two steps you listed for creating the review query completed without reporting any errors, right? (i.e. the error was in creating the new task, not in creating the query).
2. What's the starting state of your repository?

If the git repository is completely empty (i.e. you just ran git init and haven't committed anything yet) or the master branch is missing (i.e. you ran git init immediately followed by something like git checkout -b my-feature-branch), then you would see this message.

The issue in those cases is that it wants to create a new review comparing the current branch to the master branch, but the master branch doesn't exist, so it reports that using a rather opaque message.

We could support that use case (reviewing the first commit in a repository) with some code changes, but it hasn't been a high priority yet since there is a simple work-around (first commit a README file, then checkout your feature branch and commit the first code changes).

from git-appraise-eclipse.

Hi @ojarjur, sorry ... my initial description was wrong :(

The error happens if I try to create a new review task ...

I select the appraise repo and click "finish" then this error pops up. I'm using the jgitflow process for the repo ... and yes there is no master branch. So I'm at the "development" branch.

Here is my project git layout ...

What happens if the master branch is write protected?

from git-appraise-eclipse.

Currently we switched to "crucible" ... so I have not the time to try that :(

from git-appraise-eclipse.