Note on force pushing

[bors-ng]

Note on force pushing

[notriddle]

Bors doesn't need to force-push to master, though I specify "force" just to avoid crashing. This very repo has a protected master branch.

It will need to force-push to staging, but it's pretty obvious why that is.

[timvdalen]

I see, I think I figured out what was going wrong.

I had the branch protected with specific pushers.
GitHub does not allow you to (currently) add an integration user as a specific user so I turned that off.
I turned off force pushing to debug and I see the crashes on staging now.
bors just merged the first PR to master, so my install is going in the right direction :)

Thanks for the work on this and the help!

[notriddle]

Thanks for your help! I'll make a note about how it needs to be able to force-push to staging.

[timvdalen]

Just checked and it does seem to try to force push to master - I'm not sure how our configurations differ.

When I protect the master branch, I get this response for the master commit:

{\"message\":\"Cannot force-push to a protected branch\",\"documentation_url\":\"https://help.github.com/articles/about-protected-branches\"}

If I lift the protection and re-send the webhook for the status change, all is well and I see the merge commit on master.

The (force) pushed commit is a fast-forward though.

[notriddle]

Added a note to the wiki