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

branches config does not work at all #857

Closed
dogmatic69 opened this issue Jan 31, 2024 · 5 comments
Closed

branches config does not work at all #857

dogmatic69 opened this issue Jan 31, 2024 · 5 comments
Labels

Comments

@dogmatic69
Copy link

Problem Description

Unable to define branch protection rules through the branches configuration.

I've tried numerous iterations, including a direct copy/paste from the docs. No branch protection is ever created.

What is actually happening

nothing at all.

What is the expected behaviour

branch protection rules should be created / maintained by the app

Error output, if available

n/a

Context

Are you using the hosted instance of repository-settings/app or running your own?

hosted

@dogmatic69 dogmatic69 added the bug label Jan 31, 2024
@venkatamutyala
Copy link

I'm having the same problem. Assuming that it's a bug is there a way to debug/alert on when there are issues like this? I don't want to be in a situation where I think this is enabled on my repos and it turns out it's not.

@xCykrix
Copy link

xCykrix commented Apr 17, 2024

+1 as well. Even a previously known working configuration is no longer working.

@xCykrix

This comment was marked as spam.

@travi
Copy link
Member

travi commented Apr 19, 2024

is there a way to debug/alert on when there are issues like this?

that is the goal of #518, which has not been implemented yet

configuring branch protection with this app does work as long as the protection details are configured correctly and no other failures occurred before the app attempts to update the branch protection config through the api. unfortunately, there is no feedback from the app about a failure until #518 is implemented, so the best i can offer until then is to suggest removing details from your config until it works and then add details back into your config detail by detail and confirming each applies successfully.

@travi
Copy link
Member

travi commented Apr 19, 2024

duplicate of #150. please avoid opening extra issues when relevant issues already exist

@travi travi closed this as not planned Won't fix, can't repro, duplicate, stale Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants