New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make protected branch perms explicit in doc [ci skip] #8230

Closed
wants to merge 1 commit into
base: master
from

Conversation

4 participants
@cirosantilli
Contributor

cirosantilli commented Nov 3, 2014

It was not very clear that not even the owner cannot
force push or remove protected branches.

Also add force push for regular branches for symmetry.

@TeatroIO

This comment has been minimized.

TeatroIO commented Nov 3, 2014

I've prepared a stage. Click to open.

Make protected branch perms explicit in doc [ci skip]
It was not very clear that not even the owner cannot
force push or remove protected branches.

Also add force push for regular branches for symmetry.

@cirosantilli cirosantilli force-pushed the cirosantilli:protected-perms-explicit branch from 9396458 to 68e35ea Nov 3, 2014

@cirosantilli cirosantilli changed the title from Make protected branch perms explicit in doc [ci-skip] to Make protected branch perms explicit in doc [ci skip] Nov 3, 2014

@jvanbaarsen

This comment has been minimized.

Contributor

jvanbaarsen commented Dec 13, 2014

We can only accept a merge requests if all the tests are green, can you please make sure the tests of this merge requests are green? If the failing test has nothing do to with your merge request, you might want to rebase with master to see if that makes the tests green again.

@Razer6

This comment has been minimized.

Member

Razer6 commented Dec 21, 2014

@cirosantilli Could you rebase?

@cirosantilli

This comment has been minimized.

Contributor

cirosantilli commented Dec 29, 2014

Identical MR already merged: #8406

@cirosantilli cirosantilli deleted the cirosantilli:protected-perms-explicit branch Dec 29, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment