@ruweih — please don't use the master branch for pull requests; create a new feature branch (one per PR) and git rebase it on the upstream master for a cleaner history, rather than merging master into your repo's master branch, which creates multiple commits in your branch and creates a more complex history.
@ruweih — please don't use the
masterbranch for pull requests; create a new feature branch (one per PR) andgit rebaseit on the upstreammasterfor a cleaner history, rather than mergingmasterinto your repo'smasterbranch, which creates multiple commits in your branch and creates a more complex history.For details, please see: https://github.com/JanusGraph/janusgraph/blob/master/CONTRIBUTING.md#create-a-new-branch
Note that you can't change the base branch on a PR once it has been created, so you should create a new PR from a new feature branch.
Additionally, please see https://github.com/JanusGraph/janusgraph/blob/master/CONTRIBUTING.md#commit-changes-and-sign-the-developer-certificate-of-origin for how to address the failing DCO check on your PR.