---
redirect_from: "/How-to-create-a-DB-PR"
---

# How to create a DB PR via GitHub

This is a simplified guide to easily create PRs containing DB fixes (SQL code) without bothering with the terminal, 
an easier alternative to the [traditional way of creating PRs](https://www.azerothcore.org/wiki/how-to-create-a-pr).
If you want to submit C++ or other non-SQL kind of fixes, please follow the other guide.

## Do only ONCE: create your AzerothCore fork

You need to be signed on [github.com](https://github.com/). If you don't have an account yet, create one.

Open the [AzerothCore repository](https://github.com/azerothcore/azerothcore-wotlk)
and create a fork of it by clicking in the top-right "Fork" button:

![Create a fork of AzerothCore](http://www.azerothcore.org/wiki/assets/images/pr-tutorial/1.png)

## Creating a new PR

### 1. Update your fork on GitHub

Open your browser and navigate to your fork on GitHub (change `YourUsername` with your actual GitHub username):

**https://github.com/YourUsername/azerothcore-wotlk**

If your `master` branch is not up to date with latest AzerothCore, you'll see something like:

`This branch is XX commits behind azerothcore:master`

![AzerothCore update fork](http://www.azerothcore.org/wiki/assets/images/pr-tutorial/update-fork-1.png)

to update it, click on **Fetch upstream** and then **Fetch and merge**.

As a result, your fork's `master` branch should say:

`This branch is even with azerothcore:master`

![AzerothCore fork updated](http://www.azerothcore.org/wiki/assets/images/pr-tutorial/update-fork-2.png)


### 2. Create a new branch

Make sure you have the `master` branch currently selected, click on the branches dropdown and create a new branch.

![AzerothCore fork updated](http://www.azerothcore.org/wiki/assets/images/pr-tutorial/web-create-new-branch.png)

You can name your new branch the way you want (typically something related to your fix), 
just make sure you haven't used that name before and that you are creating the new branch by copying the master branch.

You should see a message like **Create branch my-new-branch-123 from master**.

After you create the new branch, make sure you **keep that one selected**.

### 3. Navigate to the pending_db_world folder

You now need to navigate inside the `data/sql/updates/pending_db_world` folder of your fork.

You can either do it manually by clicking on the `data` folder, then `sql`, `updates`, `pending_db_world`;

...or you can just open this URL (change `YourUsername` with your actual GitHub username):

**https://github.com/YourUsername/azerothcore-wotlk/tree/my-new-branch-123/data/sql/updates/pending_db_world**

### 4. Generate a new update file rev

In a new browser tab, open [azerothcore.org/pages/rev-generator](https://www.azerothcore.org/pages/rev-generator/).


![AzerothCore SQL update rev generator](http://www.azerothcore.org/wiki/assets/images/pr-tutorial/web-rev-generator.png)

This will give you:

- the name of the file you need to create which will contain your SQL code
- the *SQL version code* (an `INSERT INTO` query) which you will need to add at the top of the new SQL file that you will submit

**Note**: they should always go together and you should always have a new rev for every PR you send.
If you need to get a new rev, just refresh the page or click "Generate new".

Copy them somewhere or keep that browser tab open.

### 5. Create and commit a new file

Back on GitHub, from the `pending_db_world` folder, click **Add file** and then **Create new file**:

![AzerothCore create new SQL file](http://www.azerothcore.org/wiki/assets/images/pr-tutorial/web-create-new-file-1.png)

Now you need to:

- set the file name as the one you generated in the step 4
- add the SQL version code that you generated in the step 4
- add a new line, then add your own SQL code below and then add a new empty line at the end of the file

![AzerothCore new SQL file example](http://www.azerothcore.org/wiki/assets/images/pr-tutorial/web-create-new-file-2.png)

Now scroll down the page, you'll need to:

1. fill out the commit message, we use the [Conventional Commits format](https://www.conventionalcommits.org/),
  for example `fix(DB/Creature): some commit description here`
2. (optional) include some extra description
3. make sure that "Commit directly to the `your-new-branch-name`" is selected
4. Click **Commit new file**

![AzerothCore create new commit](http://www.azerothcore.org/wiki/assets/images/pr-tutorial/web-create-commit.png)

### 6. Open the PR

Go back to the [main AzerothCore repository](https://github.com/azerothcore/azerothcore-wotlk),
you will notice that GitHub is smart enough to realize that you are about to open a PR
and shows this nice light-yellow box:

![AzerothCore - Compare & pull request](http://www.azerothcore.org/wiki/assets/images/pr-tutorial/11.png)

click on the "Compare & pull request" green button (located on the right).

Now fill the PR template following the instructions that will appear in the screen,
do not forget to add the **testing instructions** so people can be able to test your PR and it can be merged:

![AzerothCore - Compare & pull request](http://www.azerothcore.org/wiki/assets/images/pr-tutorial/12.png)

It's also a good practice to check the "File changes" tab to see that everything is in place as you expect:

![AzerothCore - Compare & pull request](http://www.azerothcore.org/wiki/assets/images/pr-tutorial/13.png)

**NOTE:** We do not respond well to leechers! If your fix comes from another organization or person 
you should ALWAYS give credit to the original author and commit.

That's it!