> For the complete documentation index, see [llms.txt](https://docs.pullrequest.com/customer-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pullrequest.com/customer-documentation/assign-code-review-to-hackerone-code-network/requesting-project-level-code-review.md).

# Requesting Code Review for bulk files and projects

In some circumstances, you may want specific parts of a git repository reviewed by the PullRequest network outside the context of a pull/merge request (i.e., a collection of files or the entire repository).

The following steps outline the most secure way of creating a PullRequest review job within your version control hosting provide&#x72;**.**

## Steps: <a href="#steps" id="steps"></a>

**1.** Check out a local copy of the latest code for the repository that you want reviewed.

**2.** **`cd`** into your local repository's root directory.

**NOTE:** Make sure you are in the root of your local repository that is tracked by git.

**3.** Delete visible files/folders within this directory. We'll be adding them back for the code review.

**4.** Checkout and create a new branch called `deleted_code`

```
git checkout -b deleted_code
```

**5.** Add your local changes of deleting the files.

**6.** Commit these changes.

```
git commit -m "deleting all files to prepare for review"
```

**7.** Push this branch to git origin. It should now exist as a remote branch.

```
git push origin deleted_code
```

**8**. Checkout and create another branch called `code_to_review`

```
git checkout -b code_to_review
```

**9**. Grab all of the code from your main repository branch (likely `master` or `develop`).

**10**. This should have added all of the files you deleted back. Add them to git staging.

**11**. Commit changes of adding back code.

```
git commit -m "adding back files to be reviewed"
```

**12.** Push `code_to_review` branch to git origin.

```
git push origin code_to_review
```

**13.** Then open a pull/merge request in your version control hosting provider (i.e., GitHub, Bitbucket, GitLab):

![](https://blobs.gitbook.com/assets%2F-LOKbkXEfyigZ01PPnQZ%2F-LOKboW7vsg3oaGNCcDi%2F-LOKfAVqHv_fqWjE_-EC%2Fcode-review-pull-request.png?alt=media\&token=b19bbbd0-99c4-4552-9349-cb6f2d40a0d2)

**14**. Request code review from the PullRequest network by:\
\- Clicking "Request Review" in the PullRequest dashboard.\
\- Or adding **\[pr]** to the title of the pull/merge request.

![](https://blobs.gitbook.com/assets%2F-LOKbkXEfyigZ01PPnQZ%2F-LOKboW7vsg3oaGNCcDi%2F-LOKg1d52xrkB2kiG2io%2Frequest-review.png?alt=media\&token=4f19583f-b912-4921-9b27-3222bcb218ba)

Requesting review from the PullRequest dashboard
