Skip to content
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

0 Approvals required to merge Pull request by default #51

Closed
kopach opened this issue Sep 28, 2017 · 4 comments
Closed

0 Approvals required to merge Pull request by default #51

kopach opened this issue Sep 28, 2017 · 4 comments
Assignees

Comments

@kopach
Copy link

kopach commented Sep 28, 2017

As a user I don't expect that this extension will disable merge button by default. At first, I thought this is some bitbucket bug or I lost some permissions. The same situation happened with my colleagues after I recommended this extension.

How about to set 0 as required amount of approvals by default. So, once user check settings and change this value on something else - it will not be surprise why merge button not working 😄 .

@kopach
Copy link
Author

kopach commented Sep 28, 2017

Looks like similar issue but different solution: #32

@reyronald
Copy link
Member

Yeah I agree, same thing happened to me the first time.

Actually I think now BitBucket already implemented this feature themselves.

image

I'll test if the functionality is the same/as expected, and if it is, I might just remove it from the extension entirely.

@reyronald
Copy link
Member

I haven't had the time to test this yet, but just wanted to reach out to @andremw to see if you're ok with me removing the feature from the extension if it turns out that the Bitbucket first-party feature correctly replaces it, just in case, do you have anything to add ?

@reyronald reyronald self-assigned this Oct 6, 2017
@andremw
Copy link
Member

andremw commented Oct 6, 2017

100% ok! 🎉

reyronald added a commit that referenced this issue Oct 22, 2017
Feature no longer necessary since it is now implemented natively by Bitbucket with "merge checks".

Closes issue #51 and issue #32.
reyronald added a commit that referenced this issue Oct 22, 2017
Feature no longer necessary since it is now implemented natively by Bitbucket with "merge checks".

Closes issue #51 and issue #32.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants