yfii · BSCswapKi · Apr 7, 2022 · Apr 7, 2022 · Apr 7, 2022 · Apr 7, 2022
diff --git a/.env b/.env
diff --git a/.env.example b/.env.example
@@ -0,0 +1,4 @@
+REACT_APP_NETWORK_ID=56
+REACT_APP_API_URL=https://api.beefy.finance
+PUBLIC_URL=''
+IMAGE_INLINE_SIZE_LIMIT=0
diff --git a/.github/workflows/sync.yaml b/.github/workflows/sync.yaml
@@ -0,0 +1,17 @@
+name: Sync CI
+
+on: 
+  push:
+    branches: 
+      - 'prod'
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: seguido/beefy-app-sync@v0.1
+        with:
+          GITHUB_TOKEN: ${{ secrets.SYNC_GITHUB_TOKEN }}
+          GITHUB_USER: 'chebiN'
+          GITHUB_EMAIL: 'chebiN@beefy.com'
diff --git a/.gitignore b/.gitignore
@@ -1,27 +1,31 @@
-# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
-
-# dependencies
-/node_modules
-/.pnp
-.pnp.js
-
-# testing
-/coverage
-
-# production
-/build
-
-# misc
+# Global
 .DS_Store
+node_modules
+dist
+build
+
+# local env files
+.env
+.envrc
 .env.local
-.env.development.local
-.env.test.local
-.env.production.local
+.env.*.local
 
+# Log files
+*.log
 npm-debug.log*
 yarn-debug.log*
 yarn-error.log*
-scripts/upload.js
-package.json
-package-lock.json
-.idea
+pnpm-debug.log*
+
+# Editor directories and files
+.idea
+.vscode
+*.suo
+*.ntvs*
+*.njsproj
+*.sln
+*.sw?
+
+# Test
+.nyc_output
+coverage
diff --git a/.husky/.gitignore b/.husky/.gitignore
@@ -0,0 +1 @@
+_
diff --git a/.husky/pre-commit b/.husky/pre-commit
@@ -0,0 +1,4 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+yarn lint-staged
diff --git a/.nvmrc b/.nvmrc
@@ -0,0 +1 @@
+v15
diff --git a/.prettierignore b/.prettierignore
@@ -0,0 +1,9 @@
+src/features/configure/abi.js
+node_modules
+.vscode
+dist
+*.log
+*.tgz
+.envrc
+.nyc_output
+coverage
diff --git a/.prettierrc.json b/.prettierrc.json
@@ -0,0 +1,8 @@
+{
+  "trailingComma": "es5",
+  "tabWidth": 2,
+  "semi": true,
+  "singleQuote": true,
+  "printWidth": 100,
+  "arrowParens": "avoid"
+}
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -0,0 +1,56 @@
+Contributing to the Beefy App
+=======
+
+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"](https://help.github.com/articles/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-app
+git remote add upstream https://github.com/beefyfinance/beefy-app.git
+git fetch upstream
+git pull --rebase upstream master
+```
+NOTE: The directory `beefy-app` represents your fork's local copy.
+
+2) 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
+```
+
+3) 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
+```
+
+4) Go to [github.com/beefyfinance/beefy-app](https://github.com/beefyfinance/beefy-app) in your web browser and issue a new pull request.
+
+5) 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-app/issues](https://github.com/beefyfinance/beefy-app/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"](https://github.com/beefyfinance/beefy-app/issues?q=label%3A%22good+first+issue%22).
+
+## Contributor rewards 
+
+Beefy wants to be a self-sustainable community. A portion of the fees that come from running the vaults at [beefy.finance](https://app.beefy.finance) goes into a community managed treasury. The treasury is used to pay for marketing, community managers, developers, etc. We are learning together how to do this in a fair and effective way. When it comes to devs there are a few options: 
+
+1. There are some issues that will have a "Treasury Bounty" tag and a dollar amount in the issue title. This means that the issue carries a reward to the dev that closes it. 
+2. You can propose a bounty or budget to get something done by following our [proposal guidelines](PROPOSAL_GUIDELINES.md)
+3. We are tracking all contributions using [Sourcecred](https://sourcecred.io/). This is a project designed specifically to track community contributions. We have [our instance](https://beefy.finance/beefy-cred/#/explorer) and track GitHub contributions. A percentage of the treasury funds might be used every month to reward developers based on that distribution. This initiative is just getting started.
+
+Thanks for your time and code!
diff --git a/LICENSE b/LICENSE
@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) Beefy Finance
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
diff --git a/PROPOSAL_GUIDELINES.md b/PROPOSAL_GUIDELINES.md
@@ -0,0 +1,66 @@
+# Treasury Proposal Guidelines
+We are improving the ways that we reward all contributors in the Beefy community. We try to be as fair as possible and use the treasury in an effective manner.
+One of the mechanisms to reward dev work are treasury bounties. Bounties can be targeted to reward anything from a Github issue, a larger initiative, or even a developer.
+
+## When should you create a proposal?
+1. You are a dev and would like to help with a task but want or need a compensation to tackle it. 
+2. You are a dev who already did a task and would like some compensation for the effort.
+3. You are not a dev but feel like a task is particularly important and/or difficult.
+4. If you are a dev with some cred with Beefy, you can propose a regular reward for continued contributions. 
+
+## Steps
+
+### 1. Fill out a proposal
+Go to [vote.beefy.finance](https://vote.beefy.finance) and click on the big square that says "Beefy.Finance". Once you're in, click on the [New Proposal](https://vote.beefy.finance/#/beefy/create) button.
+
+#### A - Title
+Going with "Bounty of $<AMOUNT> for <ISSUE_TITLE>" is a good standard.
+
+#### B - Body
+
+You need to make clear why the community should spend those funds to help it grow or sustain itself.
+
+---
+
+Hi everyone,
+
+I'm requesting a bounty of $<AMOUNT> to reward the work of issue <ISSUE_URL>. 
+
+It's important for Beefy because...<BODY_OF_PROPOSAL>
+
+Thanks!
+
+---
+
+
+#### Choices
+
+The basic choices to give are a Yes and a No.
+
+1. Yes
+2. No
+
+Feel free to add aditional options that might make the proposal more likely to pass, or to give you additional info. for example:
+
+1. Yes, full bounty 
+2. Yes, 70% of the funds
+3. No, too expensive
+4. No, not relevant 
+
+#### Selecting Dates 
+When deciding how much time to give the community to deliverate, it's important to take budget size into account.
+
+- +$10k --> at least 7 days
+- +$5k --> at least 4 days
+- $1k-$5k --> at least 2 days
+- Less then $1k can have 24h 
+
+Unless there's a particular reason, the starting date should be pretty close to when you're creating the proposal. There's no need to wait much before the voting begins.
+
+### 2. Engage the community
+You should go to our [Discord](https://discord.gg/yq8wfHd) and engage the community on why the proposal is important. 
+The #development channel is a good place to get the attention of other beefy devs. If you can post in #citadel, that's a great place to get the atention influential members of Beefy as well.
+
+### 3. Outcome
+If the proposal passed, you'll be contacted by a member of the team, or feel free to PM anyone with the team tag on discord to move forwards
+
diff --git a/README.md b/README.md