One common use case for project maintainers is to update a broken pull request which was made by someone else.

Hub should be able to help maintainers doing the following steps:

• grab a pull request
• update the pull request (rebase or other change)
• update the pull request (aka pushing it)

$ git repo --help
No manual entry for git-repo
$ git-repo --help
....

Welcome new contributors!

In this experience, you are a doer. You take action first, and learn about the action afterwards. This design helps you get comfortable in the unknown, an entity that is omnipresent in the coding world. If you're feeling confused, that's ok. Read the instructions carefully, trust the process, and have fun!

To help guide you through the experience, th

Hacktoberfest is approaching, and so are your chances to get a free tee from Digital Ocean and DEV!

Start contributing to Open-Source by making your first Pull Request at https://www.gitstart.tech

P.S.: To win an official limited edition Hacktoberfest shirt, you must sign up on the Hacktoberfest site: https://hacktoberfest.digitalocean.com and make **four pull requests (PRs) on

Love the product so far. Was wondering if there was an action to update the base branch that a pull request is compared to? If not, I think that would be a great feature to add. Something along the lines of:

pull_request_rules:
  - name: Change base
    conditions:
      - "title~=^\\[Release\\].+"
    actions:
      change_base:
        branch: release

It would be great to have a list of commands in a help page when using git pull-request --help to know the full extent of the functionality of this package, thanks.

Split from #31

rails_best_practices has format option, so we can set a checkstyle formatter.
I find a checkstyle formatter for rails_best_practices.

https://github.com/maroekun/rails_best_practices-formatter

I'm not sure this works fine with saddler. 😓

CompatHelper can open many PRs and push all non-CompatHelper related PRs off the first page of a project's PR list. It would be great if CompatHelper labeled its auto-generated PRs with a CompatHelper label so it is easy to filter out these PRs with a simple -label:compathelper argument to the PR search.

cc: @leios @vchuravy

This could be a tag in the PR description, or in the text of a comment or review.

Need to possibly also look at review comments to cover all possible cases.