Eitan Joffe

@sbienkow-ninja - That's an unfortunate side effect of merging all the PRs in one shot. Did this leave your branch in a funky state? Did it leave your PRs in...

I wish it was like that, but github always rewrites the commit no matter what, so you can't ff. see: https://stackoverflow.com/questions/48350294/why-does-the-rebase-and-merge-option-in-github-create-new-commit-shas-is-ther/48353808. Because of this when the first pr in the...

From my understanding no-ff merges will have the same issue. The problem is that if we merge the bottom commit in the stack with no-ff, the commit gets rewritten, and...

Added logs in v0.8.4, if you can reproduce this with `--debug` flag, would be interesting to see what's going on.

if you are seeing the prompt, you should see the logs > log.Debug().Bool("stargazer", false).Msg("MaybeStar") > fmt.Print("enjoying git spr? add a GitHub star? [Y/n]:") try running: `git spr --debug status`

You are totally right! Try again with 0.8.5

This is the query used by spr to fetch starred repos: `query { viewer { starredRepositories { nodes { nameWithOwner } edges { cursor } totalCount } } }` From...

This isn't intended and is untested, but I think it should work ok as long as you rename the branch you fetched as you did. git spr doesn't store any...

@josephschmitt : looks like this is caused by TrimSpace from 1606b8ff251c2931: ``` func formatBody(commit git.Commit, stack []*github.PullRequest) string { + body := wrapInMarkdown(commit.Body) + if len(stack)

We are also integrated with jira but don't have to name the branch in any special way. We just add a "resolves: ABCD-1234" and it works really well.