# Autonomous GitHub Pull Requests

DevFeed: [Autonomous GitHub Pull Requests](<https://devfeed.tech/articles/autonomous-github-pull-requests-29353.md>)

Original publisher: [Read original article](<https://arturdryomov.dev/posts/auto-github-pull-requests/>)

Author: Artur Dryomov

Published: 2021-03-08T00:00:00Z

Content type: article

Language: en

Sources: [Artur Dryomov](<https://devfeed.tech/sources/artur-dryomov.md>)

Topics: [GitHub](<https://devfeed.tech/topics/github.md>), [pull-requests](<https://devfeed.tech/topics/pull-requests.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [GitHub Actions](<https://devfeed.tech/topics/github-actions.md>), [Code review](<https://devfeed.tech/topics/code-review.md>)

Tags: [automation](<https://devfeed.tech/tags/automation.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [github](<https://devfeed.tech/tags/github.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [pull-requests](<https://devfeed.tech/tags/pull-requests.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

## AI overview

This article describes a GitHub-based workflow for automating pull-request management. It covers automatic reviewer assignment, compiler, test, and linter checks, merge attempts based on checks and reviews, and updating other pull requests targeting the same branch.

## Source excerpt

In general, people are lazy. This is our nature -- we want to achieve more by doing less. Developers are on the next step of this urge -- we want to automate similar actions, patterns in human behavior. And what's more repetitive than working on pull requests for each source code change we make? Workflow Over time and multiple iterations I've established the following workflow. Open a PR. Assign reviewers automatically. Refine the PR. Run automatic checks (compiler, tests, linters): on success -- attempt automatic merge; on failure -- push new changes. Receive reviews: on approve -- attempt automatic merge; on decline -- push new changes. Merge the PR. Update PRs targeting the same branch. This approach reduces the manual interaction as much as possible. Developers provide changes and reviews, the automation handles everything else. There is no need to choose people for review, track checks and review statuses, merge and update remaining PRs.