https://linen.dev logo
Join Slack
Powered by
Hey, for some reason the graphite merge queue does...
# report-bugs
j
Hey, for some reason the graphite merge queue does not queue anymore. PR just sits at “will merge when ready – ready to merge”. we are only using a single ruleset for the repo and withgraphite/Graphite App is on the bypass list. any ideas? the branch rules are: • Require a pull request before merging ◦ Required approvals: 1 ◦ Require review from Code Owners (no CODEOWNERS file as of now, so this does not apply) ◦ Require conversation resolution before merging I have already removed and re-added the QueueMerge label to no avail. Happy to share PR link to private repo in a DM
p
(If applicable) To help us repro, please send the following if you haven't already: - PR links, screenshots, and/or debug output if applicable - Repro steps - Does this happen consistently? Just to you or others on your team also? - Is this a regression? Is the problem new? - If you're having an issue with the CLI, please send us debug logs using 
gt feedback --with-debug-context <any message>
Hi Josh, could you share a link to the Graphite PR page for this?
✅ 1
j
most likely a configuration issue on our end that we are not aware of
p
hmmm Im seeing 
PR BLOCKED with passing CI
 which i believe indicates graphite thought we could merge but github disagrees. Have any changes been made to the branch protection rules recently? (i assume not since i see a different PR landed shortly before this)..  could you check you CI logs to see if there is any indication of failure?
j
we do not have any CI for this repo rn
branch protection rules are fairly standard and similar to other repos where merge queue works fine
does merge queue work with the “require conversation resolution before merging” option?
p
just tested this and it seemed to work fine. Any other difference between this branch protection and the others?
j
no ci 😂
p
Have you tried to put this into the queue more than once? If not can you remove and try to re-enqueue?
j
unfortunately many times:
p
I did see that, but in my logs i only see it try to be put in the queue once 🤔 also, seems like these are all you adding the label, curious if youve tried using the UI toggle to merge when ready. Not sure there is a difference but worth a try
j
did not want to do that before you had the chance to look at the state
👍 1
maybe this is the issue: https://www.githubstatus.com/ > Update - Actions is experiencing degraded performance. We are continuing to investigate. > Investigating - We are investigating reports of degraded availability for Webhooks
p
i was thnking that as well, but the first time it failed was not in the window of their initial outage. still could definitely be a possibility, if the manual toggle also fails let me know and then lets keep an eye on the github outage as well
j
manual toggle actually added it to the queue… which is good
api requests are now also affected by the outage… so probably won't work lol
stuck in waiting for CI to complete ()
p
im seeing it as queued
j
image.png
rn… neither gh nor gt update ui when I push new versions… so we might just have to wait for the outage to resolve before investigating any further
p
yeap
j
seems to be recovering now
image.png
gonna shove it back in the queue for now
👍 1
p
Josh, i see its failed a few more times. Could you export and share the ruleset so i can best understand the settup here?
j
Copy code
{
  "id": 0,
  "name": "main requires review",
  "target": "branch",
  "source_type": "Repository",
  "source": "useorbital/catfood",
  "enforcement": "active",
  "conditions": {
    "ref_name": {
      "exclude": [],
      "include": [
        "~DEFAULT_BRANCH"
      ]
    }
  },
  "rules": [
    {
      "type": "pull_request",
      "parameters": {
        "required_approving_review_count": 1,
        "dismiss_stale_reviews_on_push": false,
        "require_code_owner_review": false,
        "require_last_push_approval": false,
        "required_review_thread_resolution": true,
        "automatic_copilot_code_review_enabled": false,
        "allowed_merge_methods": [
          "merge",
          "squash",
          "rebase"
        ]
      }
    }
  ],
  "bypass_actors": [
    {
      "actor_id": null,
      "actor_type": "OrganizationAdmin",
      "bypass_mode": "always"
    },
    {
      "actor_id": 5,
      "actor_type": "RepositoryRole",
      "bypass_mode": "always"
    },
    {
      "actor_id": 158384,
      "actor_type": "Integration",
      "bypass_mode": "always"
    }
  ]
}
p
okay, i just mimic'd this exactly and got something to merge 🤔 and to confirm, theres no actions here?
actually i just looked again and the merge went through?
j
yeah super weird
not sure why. sometimes you just gotta throw it at the wall over and over again 😂
😂 1
p
well, glad youre unblocked for now, keep us posted if it comes up again, apologies for the rough experience here 🙏
👍 1
2 Views
Open in Slack
PreviousNext
Powered by