This message was deleted.

@Adam Mustafa, which PR count is off? The number of PRs queued to merge, or number merged in the past 7 days?

Ah, I see. I figured it was the total (which would have included the 11)

It will update once they are merged!

I have problems in general merging my stack. It always fails on the second job because we use squash and merge.

cc @Jacob Gold who is working on making the merging experience for stacks more reliable.

do you have an example of a PR that failed to merge that you expected to succeed? we are working on adding better error messaging, but I can look up why specific jobs failed for now.

Sure, I'm trying right now. Those 11 PRs, the second failed.

Interesting error! I haven't seen this one before —

Command failed: git push -f origin am/replace-transactions-w-journals\nremote: error: GH007: Your push would publish a private email address.        \nremote: You can make your email public or disable this protection by visiting:        \nremote: <http://github.com/settings/emails>        \nTo <https://github.com/FinTronners/FTron>\n ! [remote rejected] am/replace-transactions-w-journals -> am/replace-transactions-w-journals (push declined due to email privacy restrictions)\nerror: failed to push some refs to '<https://github.com/FinTronners/FTron>'\n"

If it helps, after every merge I get this notification from Github:

That is because of GitHub not knowing about stacks first class. You should be able to fix the error that Jacob linked above by unchecking attached setting in

<http://github.com/settings/emails|github.com/settings/emails>

.

Re the merge conflicts message — those merge conflicts are resolved by a rebase, which the graphite merge performs automatically for you. So that notification is nothing to worry about.

That's what I figured. I assumed it was due to the squash and merge behavior

Not at all! I'm actively working on this, so it's quite helpful