linear-merge-executor

You can automate a GitHub pull request merge with Linear issue updates by using an automation script that polls CI checks, validates merge readiness, and updates the associated Linear issue status to 'Done' upon a successful merge.

Yes, you can execute a PR merge only after all CI checks pass by implementing CI polling logic that continuously checks the CI status for pull requests and blocks the merge execution until all required checks are successful.

The best way to change a Linear issue status to Done automatically after a PR merge is to use an automation tool that connects the GitHub API and Linear API, triggering the status update via the Linear API immediately following a successful merge execution.

Yes, you need GitHub and Linear API access to automate merge workflows, because the automation requires GitHub API access to perform merge operations and Linear API access to update the associated issue status.

Yes, this merge automation supports different Git merge strategies like squash, rebase, or merge, allowing you to specify the desired merge strategy during the merge execution phase to fit your branch protection rules.

An automated PR merge fails when there are branch protection rule conflicts because the merge validation phase checks for conflicts and enforces branch protection rules before executing the merge, preventing invalid or blocked merges.