OpenCompass/docs/en/notes/contribution_guide.md

Contributing to OpenCompass

• Contributing to OpenCompass
  • What is PR
  • Basic Workflow
  • Procedures in detail
    • 1. Get the most recent codebase
    • 2. Checkout a new branch from main branch
    • 3. Commit your changes
    • 4. Push your changes to the forked repository and create a PR
    • 5. Discuss and review your code
    • 6. Merge your branch to main branch and delete the branch
  • Code style
    • Python

Thanks for your interest in contributing to OpenCompass! All kinds of contributions are welcome, including but not limited to the following.

• Fix typo or bugs
• Add documentation or translate the documentation into other languages
• Add new features and components

What is PR

PR is the abbreviation of Pull Request. Here's the definition of PR in the official document of Github.

Pull requests let you tell others about changes you have pushed to a branch in a repository on GitHub. Once a pull request is opened, you can discuss and review the potential changes with collaborators and add follow-up commits before your changes are merged into the base branch.

Basic Workflow

1. Get the most recent codebase
2. Checkout a new branch from main branch.
3. Commit your changes (Don't forget to use pre-commit hooks!)
4. Push your changes and create a PR
5. Discuss and review your code
6. Merge your branch to main branch

Procedures in detail

1. Get the most recent codebase

• When you work on your first PR

  Fork the OpenCompass repository: click the fork button at the top right corner of Github page

  Clone forked repository to local

  git clone git@github.com:XXX/opencompass.git
  

  Add source repository to upstream

  git remote add upstream git@github.com:InternLM/opencompass.git
  

• After your first PR

  Checkout the latest branch of the local repository and pull the latest branch of the source repository.

  git checkout main
  git pull upstream main
  

2. Checkout a new branch from main branch

git checkout main -b branchname

3. Commit your changes

• If you are a first-time contributor, please install and initialize pre-commit hooks from the repository root directory first.

  pip install -U pre-commit
  pre-commit install
  

• Commit your changes as usual. Pre-commit hooks will be triggered to stylize your code before each commit.

  # coding
  git add [files]
  git commit -m 'messages'
  

  Sometimes your code may be changed by pre-commit hooks. In this case, please remember to re-stage the modified files and commit again.
  

4. Push your changes to the forked repository and create a PR

• Push the branch to your forked remote repository

  git push origin branchname
  

• Create a PR

• Revise PR message template to describe your motivation and modifications made in this PR. You can also link the related issue to the PR manually in the PR message (For more information, checkout the official guidance).

• You can also ask a specific person to review the changes you've proposed.

5. Discuss and review your code

• Modify your codes according to reviewers' suggestions and then push your changes.

6. Merge your branch to main branch and delete the branch

• After the PR is merged by the maintainer, you can delete the branch you created in your forked repository.

  git branch -d branchname # delete local branch
  git push origin --delete branchname # delete remote branch
  

Code style

Python

We adopt PEP8 as the preferred code style.

We use the following tools for linting and formatting:

• flake8: A wrapper around some linter tools.
• isort: A Python utility to sort imports.
• yapf: A formatter for Python files.
• codespell: A Python utility to fix common misspellings in text files.
• mdformat: Mdformat is an opinionated Markdown formatter that can be used to enforce a consistent style in Markdown files.
• docformatter: A formatter to format docstring.

Style configurations of yapf and isort can be found in setup.cfg.