🌳 Living summaries of your code in nested READMEs
📝 TODOs kept track of in issues
⏳ Keep history of an API call's result in git
📄 Summarize changes by adding a "summarize" label to a PR
🫵 Custom workflows and actions configured in YAML
Please see the installation guide.
Below is an example of AutoPR's Living README:
This folder contains a collection of files related to a Python project. The Dockerfile sets up a Docker image for running the application. The LICENSE.md file contains the MIT License for the software. The Makefile is used to automate development tasks. The action.yml file is a configuration file for an automatic pull request workflow. The autopr folder contains the main code for the autonomous agent system. The entrypoint.sh script sets up the environment and runs the application. The poetry.lock and pyproject.toml files are configuration files for the project using Poetry. There are also JSON schema files for defining strict workflows and triggers.
🏗️ Sets up a Docker image based on the duffn/python-poetry:3.9-bullseye image
🔧 Installs git from the bullseye-backports repository
📥 Copies an entrypoint script and makes it executable
📥 Copies the pyproject.toml and poetry.lock files
🔧 Activates the virtual environment and installs the project dependencies using Poetry
📥 Copies the rest of the files to the /app directory
🔧 Installs the application using Poetry
🚀 Sets the entrypoint to /entrypoint.sh for running the app
📄 This file contains the MIT License.
🔒 The license grants permission to use, modify, and distribute the software.
📝 The license requires the copyright notice and permission notice to be included in all copies.
🚫 The software is provided "as is" without warranty.
📅 The license is valid until 2023.
💼 The license is owned by Raphael Francis Ltd.
📝 This file is a makefile-like configuration file.
🔧 It defines various targets and their associated commands.
💻 The targets are: format, type, test, schema, and all.
🔧 The format target runs a command to format code using the black tool.
🔧 The type target runs a command to perform type checking using pyright.
🔧 The test target runs pytest on the autopr/tests directory.
🔧 The schema target runs a command to generate configuration entrypoints using autopr.models.config.
🔧 The all target runs all the targets in sequence: format, type, test, and schema.
🔧 This file is meant to automate common development tasks and ensure code quality.
📄 This file is a configuration file for an automatic pull request workflow.
🔧 It specifies the details for running the workflow, such as the Docker image to use.
🎨 It also includes branding information, such as the icon and color to use.
🔑 The file defines inputs required for the workflow, such as the GitHub token and base branch.
🎥 It includes a default loading GIF URL to display while the pull request is being generated.
🌿 The file defines a template for the name of the target branch.
🔄 It specifies whether to overwrite existing branches and pull requests when creating from issues.
This folder contains a collection of Python files and folders that make up an autonomous agent system. The "actions" folder contains various Python files that define different actions for the system, such as running commands and making API calls. The "gh_actions_entrypoint.py" file is the entry point for a GitHub Actions workflow. The "log_config.py" file is used to configure logging settings. The "main.py" file contains the main entry point for the application, handling triggers and workflows. The "models" folder contains data models and event handling definitions. The "services" folder contains implementations of classes for managing actions and interacting with platforms. The "triggers.py" file retrieves trigger configurations. The "workflows" folder contains YAML configuration files that define various workflows.
📝 The file is a shell script
🔧 It sets the Git configuration for a specific directory
✉️ It sets the user email and name for Git commits
📦 It activates a virtual environment
🐍 It runs a Python module called autopr.gh_actions_entrypoint
📄 This file is an executive summary of a project or report
🔍 It provides a high-level overview of the main points
📝 It highlights key findings, conclusions, and recommendations
📊 It may include a summary of data or analysis
👥 It is intended for someone who is new to the project or report
🚫 It does not include trivial details or technical explanations
💡 It gives a clear understanding of the purpose and scope of the project
👀 It provides a quick glance at the content without going into depth
💼 It serves as a starting point for further exploration or discussion
📌 It is concise and easy to read, even if the file is empty
📋 This file is a configuration file for a Python project using Poetry.
🔍 It contains information about the project's name, version, and authors.
📄 The license of the project is specified as MIT.
📦 It lists the packages and their dependencies required for the project.
🧪 There are separate dependencies for testing and development.
🔧 The build system used is Poetry.
🔍 The file also includes configuration for the Pyright static type checker.
🔍 It specifies the line length and target version for the Black code formatter.
📄 The file is a JSON schema describing a strict workflow definition.
🔍 It defines various actions that can be performed within the workflow.
🔀 Actions include commenting, setting issue titles, walking files, making API calls, running bash commands, and more.
📝 Each action has its own set of inputs and outputs.
🔄 The workflow steps are defined as an array of actions.
📚 The schema also includes definitions for various data types and declarations used within the actions.
📝 The purpose of the file is to provide a standardized structure for defining and executing strict workflows.
🗂️ The schema can be used to validate and ensure the correctness of workflow definitions.
🧩 It allows for easy integration with other tools and systems that support the schema.
📚 The file can serve as a reference for understanding the structure and capabilities of strict workflows.
📝 This file is a JSON schema definition for a trigger configuration.
📋 It defines various triggers and their corresponding actions.
🔀 Triggers include label, comment, push, and cron triggers.
📑 Each trigger can have different actions associated with it.
🚀 Actions can include commenting, setting issue titles, walking files, making API calls, running bash commands, and more.
🔗 The schema also includes definitions for various properties and fields used in the triggers and actions.
📚 The purpose of this file is to provide a standardized structure for configuring triggers and actions in a workflow or automation system.
💡 It allows users to define and customize their own triggers and actions based on their specific requirements.
📄 The schema can be used to validate and enforce the structure and format of trigger configurations in order to ensure consistency and correctness.
📄 This file is a JSON schema definition for a workflow definition.
🔧 It defines various types and properties for different actions and declarations used in the workflow.
📝 The schema includes definitions for actions like commenting, setting issue title, walking files, making API calls, running bash commands, etc.
📚 It also defines different types of declarations like template, variable, constant, and lambda declarations.
📋 The workflow definition includes a name, description, inputs, and outputs.
🔢 It consists of a list of steps which can be actions, workflow invocations, or conditional statements.
🔀 Conditional statements can have if-else branches and support different conditions like lambda expressions and context checks.
🔄 Workflow invocations can be either regular or iterable.
🔑 Overall, this file provides a structured definition for creating and executing workflows with various actions and conditions.