Deploying to gh-pages from @ 8b1c03e 🚀

.github/CONTRIBUTING.md

@@ -0,0 +1,87 @@
+## Contributing guidelines
+
+Thank you for your interest in contributing to EvalAI! Here are a few pointers about how you can help.
+
+### Setting things up
+
+To set up the development environment, follow the instructions in README.
+
+### Finding something to work on
+
+The issue tracker of EvalAI a good place to start. If you find something that interests you, comment on the thread and we’ll help get you started.
+
+Alternatively, if you come across a new bug on the site, please file a new issue and comment if you would like to be assigned. The existing issues are tagged with one or more labels, based on the part of the website it touches, its importance etc., that can help you in selecting one.
+
+If neither of these seem appealing, please post on our channel and we will help find you something else to work on.
+
+### Instructions to submit code
+
+Before you submit code, please talk to us via the issue tracker so we know you are working on it.
+
+Our central development branch is development. Coding is done on feature branches based off of development and merged into it once stable and reviewed. To submit code, follow these steps:
+
+1. Create a new branch off of development. Select a descriptive branch name.
+
+        git remote add upstream [email protected]:Cloud-CV/EvalAI.git
+        git fetch upstream
+        git checkout master
+        git merge upstream/master
+        git checkout -b your-branch-name
+
+    We highly encourage using [black](http://www.github.com/psf/black)
+    to format your code. It sticks to PEP8 for the most part and is in 
+    line with the rest of the repo. We have already set up [pre-commit 
+    hooks](https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks)
+    to run black and flake8. To activate the hooks, you just need to run
+    the following comamnd once:
+
+        pre-commit install
+
+2. Commit and push code to your branch:
+
+    - Commits should be self-contained and contain a descriptive commit message.
+        ##### Rules for a great git commit message style
+        - Separate subject from body with a blank line
+        - Do not end the subject line with a period
+        - Capitalize the subject line and each paragraph
+        - Use the imperative mood in the subject line
+        - Wrap lines at 72 characters
+        - Use the body to explain what and why you have done something. In most cases, you can leave out details about how a change has been made.
+
+        ##### Example for a commit message
+            Subject of the commit message
+
+            Body of the commit message...
+            ....
+
+    - Please make sure your code is well-formatted and adheres to PEP8 conventions (for Python) and the airbnb style guide (for JavaScript). For others (Lua, prototxt etc.) please ensure that the code is well-formatted and the style consistent.
+    - Please ensure that your code is well tested.
+    - We highly encourage to use `autopep8` to follow the PEP8 styling. Run the following command before creating the pull request:
+
+            autopep8 --in-place --exclude env,docs --recursive .     
+            git commit -a -m “{{commit_message}}”
+            git push origin {{branch_name}}
+    - Also, For Pretifying the Frontend Code Use ```HTML/JS/CSS Pretifier```.
+    - For installing the Sublime Package Control Manager in Sublime-Text Editor use [this](https://packagecontrol.io/installation#st2) link. Also, If Sublime Package Control Manager is installed then install ```HTML/JS/CSS Pretifier```.
+
+3. Once the code is pushed, create a pull request:
+
+    - On your GitHub fork, select your branch and click “New pull request”. Select “master” as the base branch and your branch in the “compare” dropdown.
+If the code is mergeable (you get a message saying “Able to merge”), go ahead and create the pull request.
+    - Check back after some time to see if the Travis checks have passed, if not you should click on “Details” link on your PR thread at the right of “The Travis CI build failed”, which will take you to the dashboard for your PR. You will see what failed / stalled, and will need to resolve them.
+    - If your checks have passed, your PR will be assigned a reviewer who will review your code and provide comments. Please address each review comment by pushing new commits to the same branch (the PR will automatically update, so you don’t need to submit a new one). Once you are done, comment below each review comment marking it as “Done”. Feel free to use the thread to have a discussion about comments that you don’t understand completely or don’t agree with.
+
+    - Once all comments are addressed, the maintainer will approve the PR.
+
+4. Once you get reviewed by a mentor and done with all the required changes, squash all the commits:
+
+            git checkout <branch_name>
+            git rebase -i HEAD~N (N is the number of commits to be squashed)
+    - Then a screen will appear with all N commits having "pick" written in front of every commit.Change pick to s for the last N-1 commits and let it be pick for the first one.
+    - Press esc button and type ":wq" to save the change and close the screen. Now a new screen will appear asking you to change commit message. Change it accordingly and save it.
+            git push origin <branch_name> --force
+
+    - For further query regarding rebasing, visit https://github.com/todotxt/todo.txt-android/wiki/Squash-All-Commits-Related-to-a-Single-Issue-into-a-Single-Commit
+    - Once rebasing is done, the reviewer will approve and merge the PR.
+
+Congratulations, you have successfully contributed to Project EvalAI!

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,14 @@
+_Thanks for taking the time to report a bug in the EvalAI project, or propose a new feature! Before creating a new issue, please do a quick search to check that it hasn't already been filed on the [issue tracker](https://github.com/Cloud-CV/EvalAI/issues)._
+
+If you'd like to report a bug, please include the following information:
+- the expected behaviour
+- the observed behaviour
+- steps to reproduce the problem
+- which operating system and/or browser you're using, if relevant
+- (if possible) copies of the console/server logs
+
+On the other hand, if you'd like to propose a new feature:
+- please describe, as clearly as possible, what you'd like to see
+- (if possible) include mockups/screenshots, if these would help convey the meaning better
+
+Thanks!

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,7 @@
+IMPORTANT NOTES (please read, then delete):
+
+* The PR title should start with "Fix #bugnum: " (if applicable), followed by a clear one-line present-tense summary of the changes introduced in the PR. For example: "Fix #bugnum: Introduce the first version of the collection editor.".
+
+* Please make sure to mention "#bugnum" somewhere in the description of the PR. This enables GitHub to link the PR to the corresponding bug.
+
+Please also make sure to follow the [style rules](https://github.com/Cloud-CV/EvalAI/blob/master/.github/CONTRIBUTING.md#style-rules).

.github/stale.yml

@@ -0,0 +1,29 @@
+# Limit to only Pull Request
+only: pulls
+
+# Number of days of inactivity a Pull Request becomes stale
+daysUntilStale: 60
+
+# Number of days of inactivity a Pull Request with the stale label is closed.
+# Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
+daysUntilClose: 7
+
+# Pull Requests with these labels will never be considered stale. Set to `[]` to disable
+exemptLabels:
+  - priority-high
+  - critical
+
+# Label to use when marking as stale
+staleLabel: inactivity
+
+pulls:
+  # Comment to post on pull requests when marking as stale. Set to `false` to disable
+  markComment: >
+    This pull request has been automatically marked as stale because it has not had
+    recent activity. It will be closed if no further activity occurs. Thank you
+    for your contributions.
+
+  # Comment to post when closing a stale Pull Request.
+  closeComment: >
+    This pull request has been automatically closed as there is no further activity. Thank you
+    for your contributions.

.github/workflows/autoupdate.yaml

@@ -0,0 +1,22 @@
+name: autoupdate
+on:
+  # Triggers if commits are pushed to master branch
+  push:
+    branches:
+      - master
+jobs:
+  autoupdate:
+    name: autoupdate
+    runs-on: ubuntu-20.04
+    steps:
+      - uses: docker://chinthakagodawita/autoupdate-action:v1
+        env:
+          GITHUB_TOKEN: '${{ secrets.GITHUB_TOKEN }}'
+          DRY_RUN: 'false'
+          PR_FILTER: 'labelled'
+          PR_LABELS: 'can-be-merged'
+          EXCLUDED_LABELS: 'needs-more-work'
+          MERGE_MSG: 'Branch was auto-updated.'
+          RETRY_COUNT: '10'
+          RETRY_SLEEP: '300'
+          MERGE_CONFLICT_ACTION: 'fail'

.github/workflows/build.yaml

@@ -0,0 +1,66 @@
+name: arenas-build
+on:
+  push:
+    branches:
+      - master
+  pull_request:
+    branches:
+      - master
+jobs:
+  build:
+    runs-on: '${{ matrix.os }}'
+    strategy:
+      matrix:
+        os:
+          - ubuntu-20.04
+        python-version:
+          - 3.7.17
+    env:
+      TRAVIS_PULL_REQUEST: ${{ vars.TRAVIS_PULL_REQUEST }}
+      TRAVIS_BRANCH: ${{ vars.TRAVIS_BRANCH }}
+      DEPLOY_FLAG: ${{ vars.DEPLOY_FLAG }}
+      PRODUCTION_INSTANCE: ${{ secrets.PRODUCTION_INSTANCE }}
+      AWS_ACCOUNT_ID: ${{ secrets.AWS_ACCOUNT_ID }}
+      AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
+      AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
+      AWS_DEFAULT_REGION: ${{ secrets.AWS_DEFAULT_REGION }}
+    steps:
+      - name: 'Set up Python ${{ matrix.python-version }}'
+        uses: actions/setup-python@v2
+        with:
+          python-version: '${{ matrix.python-version }}'
+      - run: rm -f $HOME/.cache/pip/log/debug.log
+      - name: Cache multiple paths
+        uses: actions/cache@v2
+        with:
+          path: $HOME/.cache/pip
+          key: '${{ runner.os }}-${{ hashFiles(''TODO'') }}'
+      - uses: actions/checkout@v2
+      - run: sudo rm -f /etc/boto.cfg
+      - run: export CHROME_BIN=chromium-browser
+      - run: export DISPLAY=:99.0
+      - run: pip install awscli==1.18.66 importlib-metadata==4.8.3 flake8==3.8.4 coveralls==3.3.1
+      - run: flake8 ./ || exit 1;
+#      - run: >-
+#          if [ $TRAVIS_PULL_REQUEST = false ]; then echo $DOCKER_PASSWORD
+#          | docker login --username $DOCKER_USERNAME --password-stdin ||
+#          exit 1; fi
+      - name: Configure AWS Credentials
+        uses: aws-actions/configure-aws-credentials@v4
+        with:
+          aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }}
+          aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
+          aws-region: ${{ secrets.AWS_DEFAULT_REGION }}
+      - name: Login to ECR
+        uses: docker/login-action@v3
+        with:
+          registry: ${{ secrets.AWS_REGISTRY }}
+      - run: docker-compose build || exit 1;
+      - run: docker-compose run nodejs bash -c "gulp dev && karma start --single-run && gulp staging" || exit 1;
+      - run: docker-compose run -e DJANGO_SETTINGS_MODULE=settings.test django pytest --cov . --cov-config .coveragerc || exit 1;
+      - run: 'bash <(curl -s https://codecov.io/bash)'
+      - run: coveralls --rcfile=.coveragerc
+      - run: eval "$(ssh-agent -s)"
+      - run: openssl enc -d -aes-256-cbc -K ${{ secrets.ENCRYPTED_KEY }} -iv ${{ secrets.ENCRYPTED_IV }} -in scripts/deployment/evalai.pem.enc -out scripts/deployment/evalai.pem || true
+      - run: ./scripts/deployment/push.sh
+      - run: ./scripts/deployment/deploy.sh ${{ vars.DEPLOY_FLAG }}

404.html

@@ -0,0 +1,15 @@
+<!DOCTYPE html>
+<html lang="en" class="dark">
+  <head>
+    <meta charset="UTF-8">
+    <link rel="icon" href="/favicon.ico">
+    <meta name="viewport" content="width=device-width, initial-scale=1.0">
+    <title>Arena</title>
+    <script type="module" crossorigin src="/assets/index-7e538ac2.js"></script>
+    <link rel="stylesheet" href="/assets/index-be0a3cd5.css">
+  </head>
+  <body>
+    <div id="app"></div>
+
+  </body>
+</html>