LogoLogo
Visit PullRequest.comApp Dashboard
  • Welcome to HackerOne Code!
  • Frequently Asked Questions
    • Supported Integrations
    • What to Expect
      • How to Get More Out of Code Review
  • Getting Started
    • Supported Languages
    • Create an Account
  • Cloud Integrations
    • Adding GitHub Repositories
    • Adding Bitbucket Repositories
    • Adding GitLab Projects
    • Adding Azure DevOps Repositories
  • On-Premise Integration
  • On-Premise Support
  • Assign Code Reviews to PullRequest Network
    • Assigning Reviews to HackerOne Code
    • Code Review Statuses
    • Collaborating with HackerOne Reviewers
    • Rating Reviews
    • Requesting Code Review for bulk files and projects
  • Code Review Settings
    • Advanced Review Settings
    • Project Notes Access
    • Repository Search
    • PullRequest Approval
    • Exclude Files from HackerOne Review
  • Metrics
    • Benchmarks
    • Terms
Powered by GitBook
On this page
  • How fast is PullRequest?
  • What do reviews from your engineers look like?
  • Can I see some examples?
  • What are PullRequest Reviewers like?
  • Do reviewers approve pull requests?
  • Do you have a trial period?
  1. Frequently Asked Questions

What to Expect

PreviousSupported IntegrationsNextHow to Get More Out of Code Review

Last updated 4 years ago

How fast is PullRequest?

We aim to turn around pull/merge requests as fast as possible. For most requests, that’ll be within a few hours.

Factors that contribute to this are:

  • The size of the pull/merge request.

  • The complexity of the code changes.

  • The expertise required to review the code.

What do reviews from your engineers look like?

Think of PullRequest as an extension of your current team. One or more engineers will be reviewing your code before it is merged.

Our reviewers are posted in your source control provider alongside your internal developers; and you'll be able communicate with them similarly.

Can I see some examples?

Yes!

What to see something specific? Let us know: support@pullrequest.com

What are PullRequest Reviewers like?

PullRequest reviewers are all US-based, senior-level software engineers with 5+ years* experience building complex applications and systems.

PullRequest reviewers are distributed throughout the US with notable concentrations in the San Francisco, Silicon Valley, Oakland, New York, Seattle, Boston, Los Angeles, and Denver.

Members come from a variety of backgrounds and include:

  • Serial technical founders

  • Major language/framework maintainers

  • CS PhDs

  • Technical project owners at companies like Google, SpaceX, Amazon, Spotify, Uber, Instagram, Square, Dropbox, Microsoft, Zynga, Coursera, NASA, Lockheed Martin, Bloomberg, Moz, Procore, and many, many more.

Here are some guest contributions our reviewers have made to the PullRequest blog:

* With rare and extraordinary exceptions.

Do reviewers approve pull requests?

Currently, our reviewers do not approve or reject pull/merge requests.

This is because every team has a unique workflow for pushing and approving updates to their repositories, including things like running automated tests to make sure each build passes and approval of individuals with code ownership.

That said it is possible to work PullRequest into branch approval flows, and we encourage teams to do so if desired.

For example, many teams will use version control tools to request changes or reject the branch if PullRequest has found issues that need to be addressed. Either the code author or an appointed individual will perform the action.

We're happy to help advise your team on how to best do this based on your workflow. Please reach out to support@pullrequest.com.

Do you have a trial period?

by by by by by

Most organizations qualify for a no-obligation PullRequest trial. To see if you qualify, with a member of our team.

https://github.com/oughtinc/ergo/pull/61
https://github.com/oughtinc/ergo/pull/55
https://github.com/Unity-Technologies/unity-cache-server/pull/36
https://github.com/commons-app/apps-android-commons/pull/3046
What To Look For When Reviewing C#
Artak Mkrtchyan
How to Write a Good Code Comment
Tyler Adams
Writing A Great Pull Request Description
Gonzalo BaƱuelos
The Top 5 Mistakes Made in Angular Projects
Alain Chautard
Top 3 Security Vulnerabilities I Find in iOS and Android Projects
Chris Griffith
schedule a call