sth

.devcontainer/Dockerfile

@@ -0,0 +1,23 @@
+# [Choice] Python version (use -bullseye variants on local arm64/Apple Silicon): 3, 3.10, 3.9, 3.8, 3.7, 3.6, 3-bullseye, 3.10-bullseye, 3.9-bullseye, 3.8-bullseye, 3.7-bullseye, 3.6-bullseye, 3-buster, 3.10-buster, 3.9-buster, 3.8-buster, 3.7-buster, 3.6-buster
+ARG VARIANT=3-bullseye
+FROM python:3.8
+
+RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+ # Remove imagemagick due to https://security-tracker.debian.org/tracker/CVE-2019-10131
+ && apt-get purge -y imagemagick imagemagick-6-common 
+
+# Temporary: Upgrade python packages due to https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-40897
+# They are installed by the base image (python) which does not have the patch.
+RUN python3 -m pip install --upgrade setuptools
+
+# [Optional] If your pip requirements rarely change, uncomment this section to add them to the image.
+# COPY requirements.txt /tmp/pip-tmp/
+# RUN pip3 --disable-pip-version-check --no-cache-dir install -r /tmp/pip-tmp/requirements.txt \
+# && rm -rf /tmp/pip-tmp
+
+# [Optional] Uncomment this section to install additional OS packages.
+# RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
+# && apt-get -y install --no-install-recommends <your-package-list-here>
+
+# [Optional] Uncomment this line to install global node packages.
+# RUN su vscode -c "source /usr/local/share/nvm/nvm.sh && npm install -g <your-package-here>" 2>&1

.devcontainer/devcontainer.json

@@ -0,0 +1,39 @@
+{
+ "build": {
+ "dockerfile": "./Dockerfile",
+ "context": "."
+ },
+ "features": {
+ "ghcr.io/devcontainers/features/common-utils:2": {
+ "installZsh": "true",
+ "username": "vscode",
+ "userUid": "1000",
+ "userGid": "1000",
+ "upgradePackages": "true"
+ },
+ "ghcr.io/devcontainers/features/python:1": "none",
+ "ghcr.io/devcontainers/features/node:1": "none",
+ "ghcr.io/devcontainers/features/git:1": {
+ "version": "latest",
+ "ppa": "false"
+ }
+ },
+ // Configure tool-specific properties.
+ "customizations": {
+ // Configure properties specific to VS Code.
+ "vscode": {
+ // Set *default* container specific settings.json values on container create.
+ "settings": {
+ "python.defaultInterpreterPath": "/usr/local/bin/python"
+ }
+ }
+ },
+ // Use 'forwardPorts' to make a list of ports inside the container available locally.
+ // "forwardPorts": [],
+
+ // Use 'postCreateCommand' to run commands after the container is created.
+ // "postCreateCommand": "pip3 install --user -r requirements.txt",
+
+ // Set `remoteUser` to `root` to connect as root instead. More info: https://aka.ms/vscode-remote/containers/non-root.
+ "remoteUser": "vscode"
+}

.flake8

@@ -0,0 +1,12 @@
+[flake8]
+max-line-length = 88
+extend-ignore = E203
+exclude =
+ .tox,
+ __pycache__,
+ *.pyc,
+ .env
+ venv/*
+ .venv/*
+ reports/*
+ dist/*

.github/FUNDING.yml

@@ -0,0 +1,3 @@
+# These are supported funding model platforms
+
+github: Torantulino

.github/ISSUE_TEMPLATE/1.bug.yml

@@ -0,0 +1,60 @@
+name: Bug report 🐛
+description: Create a bug report for Auto-GPT.
+labels: ['status: needs triage']
+body:
+ - type: checkboxes
+ attributes:
+ label: ⚠️ Search for existing issues first ⚠️
+ description: >
+ Please [search the history](https://github.com/Torantulino/Auto-GPT/issues)
+ to see if an issue already exists for the same problem.
+ options:
+ - label: I have searched the existing issues, and there is no existing issue for my problem
+ required: true
+ - type: markdown
+ attributes:
+ value: |
+ Please provide a searchable summary of the issue in the title above ⬆️.
+
+ ⚠️ SUPER-busy repo, please help the volunteer maintainers.
+ The less time we spend here, the more time we spend building AutoGPT.
+ 
+ Please help us help you:
+ - Does it work on `stable` branch (https://github.com/Torantulino/Auto-GPT/tree/stable)?
+ - Does it work on current `master` (https://github.com/Torantulino/Auto-GPT/tree/master)?
+ - Search for existing issues, "add comment" is tidier than "new issue"
+ - Ask on our Discord (https://discord.gg/autogpt)
+ - Provide relevant info:
+ - Provide commit-hash (`git rev-parse HEAD` gets it)
+ - If it's a pip/packages issue, provide pip version, python version
+ - If it's a crash, provide traceback.
+ - type: checkboxes
+ attributes:
+ label: GPT-3 or GPT-4
+ description: >
+ If you are using Auto-GPT with `--gpt3only`, your problems may be caused by
+ the limitations of GPT-3.5
+ options:
+ - label: I am using Auto-GPT with GPT-3 (GPT-3.5)
+ - type: textarea
+ attributes:
+ label: Steps to reproduce 🕹
+ description: |
+ **⚠️ Issues that we can't reproduce will be closed.**
+ - type: textarea
+ attributes:
+ label: Current behavior 😯
+ description: Describe what happens instead of the expected behavior.
+ - type: textarea
+ attributes:
+ label: Expected behavior 🤔
+ description: Describe what should happen.
+ - type: textarea
+ attributes:
+ label: Your prompt 📝
+ description: |
+ If applicable please provide the prompt you are using. You can find your last-used prompt in last_run_ai_settings.yaml.
+ value: |
+ ```yaml
+ # Paste your prompt here
+ ```

.github/ISSUE_TEMPLATE/2.feature.yml

@@ -0,0 +1,29 @@
+name: Feature request 🚀
+description: Suggest a new idea for Auto-GPT.
+labels: ['status: needs triage']
+body:
+ - type: markdown
+ attributes:
+ value: |
+ Please provide a searchable summary of the issue in the title above ⬆️.
+
+ Thanks for contributing by creating an issue! ❤️
+ - type: checkboxes
+ attributes:
+ label: Duplicates
+ description: Please [search the history](https://github.com/Torantulino/Auto-GPT/issues) to see if an issue already exists for the same problem.
+ options:
+ - label: I have searched the existing issues
+ required: true
+ - type: textarea
+ attributes:
+ label: Summary 💡
+ description: Describe how it should work.
+ - type: textarea
+ attributes:
+ label: Examples 🌈
+ description: Provide a link to other implementations, or screenshots of the expected behavior.
+ - type: textarea
+ attributes:
+ label: Motivation 🔦
+ description: What are you trying to accomplish? How has the lack of this feature affected you? Providing context helps us come up with a solution that is more useful in the real world.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,33 @@
+<!-- 📢 Announcement
+We've recently noticed an increase in pull requests focusing on combining multiple changes. While the intentions behind these PRs are appreciated, it's essential to maintain a clean and manageable git history. To ensure the quality of our repository, we kindly ask you to adhere to the following guidelines when submitting PRs:
+
+Focus on a single, specific change.
+Do not include any unrelated or "extra" modifications.
+Provide clear documentation and explanations of the changes made.
+Ensure diffs are limited to the intended lines — no applying preferred formatting styles or line endings (unless that's what the PR is about).
+For guidance on committing only the specific lines you have changed, refer to this helpful video: https://youtu.be/8-hSNHHbiZg
+
+By following these guidelines, your PRs are more likely to be merged quickly after testing, as long as they align with the project's overall direction. -->
+
+### Background
+<!-- Provide a concise overview of the rationale behind this change. Include relevant context, prior discussions, or links to related issues. Ensure that the change aligns with the project's overall direction. -->
+
+### Changes
+<!-- Describe the specific, focused change made in this pull request. Detail the modifications clearly and avoid any unrelated or "extra" changes. -->
+
+### Documentation
+<!-- Explain how your changes are documented, such as in-code comments or external documentation. Ensure that the documentation is clear, concise, and easy to understand. -->
+
+### Test Plan
+<!-- Describe how you tested this functionality. Include steps to reproduce, relevant test cases, and any other pertinent information. -->
+
+### PR Quality Checklist
+- [ ] My pull request is atomic and focuses on a single change.
+- [ ] I have thoroughly tested my changes with multiple different prompts.
+- [ ] I have considered potential risks and mitigations for my changes.
+- [ ] I have documented my changes clearly and comprehensively.
+- [ ] I have not snuck in any "extra" small tweaks changes <!-- Submit these as separate Pull Requests, they are the easiest to merge! -->
+
+<!-- If you haven't added tests, please explain why. If you have, check the appropriate box. If you've ensured your PR is atomic and well-documented, check the corresponding boxes. -->
+
+<!-- By submitting this, I agree that my pull request should be closed if I do not fill this out or follow the guide lines. -->

.github/workflows/auto_format.yml

@@ -0,0 +1,23 @@
+name: auto-format
+on: pull_request
+jobs:
+ format:
+ runs-on: ubuntu-latest
+ steps:
+ - name: Checkout PR branch
+ uses: actions/checkout@v2
+ with:
+ ref: ${{ github.event.pull_request.head.sha }}
+ - name: autopep8
+ uses: peter-evans/autopep8@v1
+ with:
+ args: --exit-code --recursive --in-place --aggressive --aggressive .
+ - name: Check for modified files
+ id: git-check
+ run: echo "modified=$(if git diff-index --quiet HEAD --; then echo "false"; else echo "true"; fi)" >> $GITHUB_ENV
+ - name: Push changes
+ if: steps.git-check.outputs.modified == 'true'
+ run: |
+ git config --global user.name 'Torantulino'
+ git config --global user.email '[email protected]'
+ git remote set

.github/workflows/ci.yml

@@ -0,0 +1,44 @@
+name: Python CI
+
+on:
+ push:
+ branches:
+ - master
+ pull_request:
+ branches:
+ - master
+
+jobs:
+ build:
+ runs-on: ubuntu-latest
+
+ strategy:
+ matrix:
+ python-version: [3.8]
+
+ steps:
+ - name: Check out repository
+ uses: actions/checkout@v2
+
+ - name: Set up Python ${{ matrix.python-version }}
+ uses: actions/setup-python@v2
+ with:
+ python-version: ${{ matrix.python-version }}
+
+ - name: Install dependencies
+ run: |
+ python -m pip install --upgrade pip
+ pip install -r requirements.txt
+
+ - name: Lint with flake8
+ continue-on-error: false
+ run: flake8 autogpt/ tests/ --select E303,W293,W291,W292,E305,E231,E302
+
+ - name: Run unittest tests with coverage
+ run: |
+ coverage run --source=autogpt -m unittest discover tests
+
+ - name: Generate coverage report
+ run: |
+ coverage report
+ coverage xml

.github/workflows/docker-image.yml

@@ -0,0 +1,18 @@
+name: Docker Image CI
+
+on:
+ push:
+ branches: [ "master" ]
+ pull_request:
+ branches: [ "master" ]
+
+jobs:
+
+ build:
+
+ runs-on: ubuntu-latest
+
+ steps:
+ - uses: actions/checkout@v3
+ - name: Build the Docker image
+ run: docker build . --file Dockerfile --tag autogpt:$(date +%s)

.github/workflows/dockerhub-imagepush.yml

@@ -0,0 +1,24 @@
+name: Push Docker Image on Release
+
+on:
+ push:
+ branches: [ "stable" ]
+
+jobs:
+
+ build:
+
+ runs-on: ubuntu-latest
+
+ steps:
+ - uses: actions/checkout@v3
+ - name: Log in to Docker hub
+ env:
+ DOCKER_USER: ${{secrets.DOCKER_USER}}
+ DOCKER_PASSWORD: ${{secrets.DOCKER_PASSWORD}}
+ run: |
+ docker login -u $DOCKER_USER -p $DOCKER_PASSWORD
+ - name: Build the Docker image
+ run: docker build . --file Dockerfile --tag ${{secrets.DOCKER_USER}}/auto-gpt:$(git describe --tags `git rev-list --tags --max-count=1`)
+ - name: Docker Push
+ run: docker push ${{secrets.DOCKER_USER}}/auto-gpt