[GraphQL API] CreateBranchProtectionRuleInput and UpdateBranchProtectionRuleInput should support merge queue configurations #77614
-
Select Topic AreaProduct Feedback BackgroundMergeQueue and its related resource types was added to the GraphQL API on 2023-04-13: https://docs.github.com/en/graphql/overview/changelog#schema-changes-for-2023-04-13-1 ProblemI'm trying to utilize GraphQL API to create branch protection rules with merge queue configurations, but realized CreateBranchProtectionRuleInput and UpdateBranchProtectionRuleInput currently does not support merge queue configurations Requestadd merge queue configuration support to |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 4 replies
-
you mean like this ? `input CreateBranchProtectionRuleInput { input UpdateBranchProtectionRuleInput { |
Beta Was this translation helpful? Give feedback.
-
kind of, except merge queue doesn't have a name (it's just attached to the branch protection rules), there are additional configurations that should be also included. See MergeQueueConfiguration Object and screenshot below: |
Beta Was this translation helpful? Give feedback.
-
Hi @zhpeng811, Thanks so much for sharing your feedback here in the community. I'll get this filed with the appropriate teams so that this is on their radar. Cheers! 🚀 |
Beta Was this translation helpful? Give feedback.
-
FYI- this heavily crosses over with https://github.com/orgs/community/discussions/50893 . A concrete use case where this would be useful is in integrations/terraform-provider-github#1481 |
Beta Was this translation helpful? Give feedback.
-
merge queue support have been added for rulesets:https://docs.github.com/en/graphql/reference/enums#repositoryruletype and since branch protection and ruleset are very similar GitHub probably won't add support to it, marking this discussion as resolved |
Beta Was this translation helpful? Give feedback.
merge queue support have been added for rulesets:https://docs.github.com/en/graphql/reference/enums#repositoryruletype
and since branch protection and ruleset are very similar GitHub probably won't add support to it, marking this discussion as resolved