Yicong-Huang commented on PR #5050: URL: https://github.com/apache/texera/pull/5050#issuecomment-4438009485
Additional investigation on the remaining `/rules/2` error: - This PR keeps the `merge_queue` rule; it only fixes the surrounding ruleset payload issues. - I validated through the GitHub API on the fork that the non-merge-queue portion of the payload can create a temporary disabled ruleset once `integration_id: -1`, `do_not_enforce_on_create`, and response-only `source_type/source` are removed. - I then tested a minimal GraphQL `CreateRepositoryRulesetInput` containing only a `MERGE_QUEUE` rule. GitHub still returned `Invalid rules: 'Merge queue'`.\n- Classic branch protection GraphQL inputs do not expose a `requiresMergeQueue` field, so rulesets appear to be the only API-visible path.\n\nThis means #5050 should address the `/rules/3` and `/rules/5` schema errors, but if ASF Infra still sees `/rules/2` for `merge_queue`, that likely requires Infra/GitHub-side support for creating merge queue rules rather than another Texera YAML shape change. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
