Skip to content

Latest commit

 

History

History
48 lines (32 loc) · 2.19 KB

CONTRIBUTING.md

File metadata and controls

48 lines (32 loc) · 2.19 KB

Contributing to beefy-moobird

We really appreciate and value contributions to the Beefy.Finance repositories. Please take 5' to review the items listed below to make sure that your contributions are merged as soon as possible.

Creating Pull Requests (PRs)

As a contributor, you are expected to fork this repository, work on your own fork and then submit pull requests. The pull requests will be reviewed and eventually merged into the main repo. See "Fork-a-Repo" for how this works.

A typical workflow

  1. Make sure your fork is up to date with the main repository:
cd beefy-moobird
git remote add upstream https://github.com/beefyfinance/beefy-moobird.git
git fetch upstream
git pull --rebase upstream main

NOTE: The directory beefy-moobird represents your fork's local copy.

  1. Branch out from master into fix/some-bug-#123: (Postfixing #123 will associate your PR with the issue #123 and make everyone's life easier =D)
git checkout -b fix/some-bug-#123
  1. Make your changes, add your files, commit, and push to your fork.
git add SomeFile.js
git commit "Fix some bug #123"
git push origin fix/some-bug-#123
  1. Go to github.com/beefyfinance/beefy-moobird in your web browser and issue a new pull request.

  2. Maintainers will review your code and possibly ask for changes before your code is pulled in to the main repository. We'll check that all tests pass, review the coding style, and check for general code correctness. If everything is OK, we'll merge your pull request and your code will be part of Beefy's App.

IMPORTANT Please pay attention to the maintainer's feedback, since its a necessary step to keep up with the standards Beefy.Finance attains to.

All set!

If you have any questions, feel free to post them to github.com/beefyfinance/beefy-moobird/issues.

Finally, if you're looking to collaborate and want to find easy tasks to start, look at the issues we marked as "Good first issue".

Thanks for your time and code!