Skip to content

How to Contribute

Before you get started

File an issue on the github or forum

You are welcome to contribute any code or files to the project. But first we suggest you raise an issue on the github or on the forum to start a discussion with the community. Check through the topic for Github.

Sign the Contributor License Agreement (CLA)

What is CLA?

Here is the vesoft inc. Contributor License Agreement.

Click the Sign in with GitHub to agree button to sign the CLA.

If you have any question, send an email to

Step 1: Fork in the

The Nebula Graph project has many repositories. Take the graph engine repository for example:

  1. Visit
  2. Click the Fork button (top right) to establish an online fork.

Step 2: Clone Fork to Local Storage

Define a local working directory:

# Define your working directory

Set user to match your Github profile name:

user={your Github profile name}

Create your clone:

mkdir -p $working_dir
cd $working_dir
git clone$user/nebula-graph.git
# the following is recommended
# or: git clone$user/nebula-graph.git

cd $working_dir/nebula
git remote add upstream
# or: git remote add upstream

# Never push to upstream master since you do not have write access.
git remote set-url --push upstream no_push

# Confirm that your remotes make sense:
# It should look like:
# origin$(user)/nebula-graph.git (fetch)
# origin$(user)/nebula-graph.git (push)
# upstream (fetch)
# upstream  no_push (push)
git remote -v

Define a Pre-Commit Hook

Please link the Nebula Graph pre-commit hook into your .git directory.

This hook checks your commits for formatting, building, doc generation, etc.

cd $working_dir/nebula-graph/.git/hooks
ln -s $working_dir/nebula-graph/.linters/cpp/hooks/ .

Sometimes, pre-commit hook can not be executable. You have to make it executable manually.

cd $working_dir/nebula-graph/.git/hooks
chmod +x pre-commit

Step 3: Branch

Get your local master up to date:

cd $working_dir/nebula-graph
git fetch upstream
git checkout master
git rebase upstream/master

Checkout a new branch from master:

git checkout -b myfeature

NOTE: Because your PR often consists of several commits, which might be squashed while being merged into upstream, we strongly suggest you open a separate topic branch to make your changes on. After merged, this topic branch could be just abandoned, thus you could synchronize your master branch with upstream easily with a rebase like above. Otherwise, if you commit your changes directly into master, maybe you must use a hard reset on the master branch, like:

git fetch upstream
git checkout master
git reset --hard upstream/master
git push --force origin master

Step 4: Develop

Code Style

We adopt cpplint to make sure that the project conforms to Google's coding style guides. The checker will be implemented before the code is committed.

Unit Tests Required

Please add unit tests for your new features or bug fixes.

Build Your Code with Unit Tests Enable

Please refer to the build source code documentation to compile.

Make sure you have enabled the build of unit tests by setting -DENABLE_TESTING=ON.

Run Tests

In the root folder of nebula-graph , run the following command:

ctest -j$(nproc)

Step 5: Bring Your Branch Update to Date

# While on your myfeature branch.
git fetch upstream
git rebase upstream/master

You need to bring the head branch up to date after other collaborators merge pull requests to the base branch.

Step 6: Commit

Commit your changes.

git commit -a

Likely you'll go back and edit/build/test some more than --amend in a few cycles.

Step 7: Push

When ready to review (or just to establish an offsite backup or your work), push your branch to your fork on

git push origin myfeature

Step 8: Create a Pull Request

  1. Visit your fork at$user/nebula-graph (replace $user obviously).
  2. Click the Compare & pull request button next to your myfeature branch.

Step 9: Get a Code Review

Once your pull request has been opened, it will be assigned to at least two reviewers. Those reviewers will do a thorough code review to make sure that the changes meet the repository's contributing guidelines and other quality standards.

Last update: April 7, 2021
Back to top