Skip to content

Latest commit

 

History

History
116 lines (78 loc) · 4.9 KB

CONTRIBUTING.md

File metadata and controls

116 lines (78 loc) · 4.9 KB
Raw

AKG contributing guidelines

Contributor License Agreement

It's required to sign CLA before your first code submission to MindSpore community.

For individual contributor, please refer to ICLA online document for the detailed information.

Getting Started

  • Fork the repository on Github or Gitee.
  • Read the README.md for project information and build instructions.

Contribution Workflow

Code style

Please follow this style to make AKG easy to review, maintain and develop.

Fork-Pull development model

  • Fork AKG repository

    Before submitting code to AKG project, please make sure that this project have been forked to your own repository. It means that there will be parallel development between AKG repository and your own repository, so be careful to avoid the inconsistency between them.

  • Clone the remote repository

    If you want to download the code to the local machine, git is the best way:

    # For GitHub
git clone https://github.com/{insert_your_forked_repo}/akg.git
git remote add upstream https://github.com/mindspore-ai/akg.git
# For Gitee
git clone https://gitee.com/{insert_your_forked_repo}/akg.git
git remote add upstream https://gitee.com/mindspore/akg.git

  • Develop code locally

    To avoid inconsistency between multiple branches, checking out to a new branch is SUGGESTED:

    git checkout -b {new_branch_name} origin/master

    Then you can change the code arbitrarily.

  • Push the code to the remote repository

    After updating the code, you should push the update in the formal way:

    git add .
git status # Check the update status
git commit -m "Your commit title"
git commit -s --amend #Add the concrete description of your commit
git push origin {new_branch_name}

  • Pull a request to AKG repository

    In the last step, your need to pull a compare request between your new branch and AKG master branch. After finishing the pull request, the Jenkins CI will be automatically set up for building test.

Report issues

A great way to contribute to the project is to send a detailed report when you encounter an issue. We always appreciate a well-written, thorough bug report, and will thank you for it!

When reporting issues, refer to this format:

  • What version of env (akg, os, python etc) are you using?
  • Is this a BUG REPORT or FEATURE REQUEST?
  • What happened?
  • What you expected to happen?
  • How to reproduce it?(as minimally and precisely as possible)
  • Special notes for your reviewers?

Issues advisory:

  • If you find an unclosed issue, which is exactly what you are going to solve, please put some comments on that issue to tell others you would be in charge of it.
  • If an issue is opened for a while, it's recommended for contributors to precheck before working on solving that issue.
  • If you resolve an issue which is reported by yourself, it's also required to let others know before closing that issue.

Propose PRs

  • Raise your idea as an issue on GitHub or Gitee
  • If it is a new feature that needs lots of design details, a design proposal should also be submitted.
  • After reaching consensus in the issue discussions and design proposal reviews, complete the development on the forked repo and submit a PR.
  • None of PRs is not permitted until it receives 2+ LGTM from approvers. Please NOTICE that approver is NOT allowed to add LGTM on his own PR.
  • After PR is sufficiently discussed, it will get merged, abandoned or rejected depending on the outcome of the discussion.

PRs advisory:

  • Any irrelevant changes should be avoided.
  • Make sure your commit history being ordered.
  • Always keep your branch up with the master branch.
  • For bug-fix PRs, make sure all related issues being linked.