ref:main

fetch-depth:1

-name:AutoPR

uses:raphael-francis/autopr-internal@main

uses:irgolic/autopr@main

env:

OPENAI_API_KEY:${{ secrets.OPENAI_API_KEY }}

with:

This folder contains files and folders related to a workflow automation system. It provides reusable actions, triggers, and workflows for different automation scenarios. The files include configuration files for Docker images, licenses, makefile-like tasks, automatic pull request workflows, shell scripts, project dependencies, workflow schemas, and more. The folder also includes a collection of Python files for defining actions, triggers, and workflows, as well as services for managing and running automated actions. Overall, this folder supports the development and execution of automated workflows with various actions and conditions.

🏗️ Sets up a Docker image based on the`duffn/python-poetry:3.9-bullseye` image

🔧 Installs git from the bullseye-backports repository

🚀 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 is owned by Raphael Francis Ltd.

📝 This file is a makefile-like configuration file.

🔧 It defines various targets and their associated commands.

🔧 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 specifies whether to overwrite existing branches and pull requests when creating from issues.

This folder contains a collection of Python files and folders related to a workflow automation system. It includes files for defining actions, triggers, and workflows, as well as services for managing and running automated actions. There are also files for configuring logging settings, defining data models, and interacting with the GitHub platform. Overall, this folder provides a range of reusable actions, triggers, and workflows for different automation scenarios, along with the necessary services and utilities to support them.

📝 The file is a shell script

🔧 It sets the Git configuration for a specific directory

🐍 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 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.

🔍 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.

📚 The file can serve as a reference for understanding the structure and capabilities of strict workflows.

📋 The file is a JSON schema that describes a configuration for triggers and actions in a workflow.

🔗 It includes definitions for various action models such as comment, set_issue_title, walk_files, make_api_call, bash, etc.

💻 Overall, this file is a powerful tool for defining and configuring automated workflows with various triggers and actions.

📄 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.

This folder contains a collection of Python files and folders related to a workflow automation system. It includes files for defining actions, triggers, and workflows, as well as services for managing and running automated actions. There are also files for configuring logging settings, defining data models, and interacting with the GitHub platform. Overall, this folder provides a range of reusable actions, triggers, and workflows for different automation scenarios, along with the necessary services and utilities to support them.

This file is empty.

This folder contains a collection of Python files that implement various actions for automating tasks. Each file represents a different action, such as running a bash command, generating choices based on user prompts, publishing comments on GitHub issues, committing and pushing changes to a remote repository, searching for specific keywords in files, inserting content into strings, and more. The files define classes that encapsulate the logic for each action, and they often include input and output models for data validation. Some files also include example usage and test cases. Additionally, there are utility files for managing prompt context and listing files in a folder. Overall, the folder provides a range of reusable actions for different automation scenarios.

📄 This file is the entry point for a GitHub Actions workflow.

🔧 It contains the main logic for running the workflow.

🔒 The GitHub token is used for authentication and authorization.

📝 This file is used to configure logging settings and create loggers.

🔧 It imports the necessary modules for logging and structlog.

🔧 The configure_logging function is called to configure logging on module import.

📋 This file contains the implementation of the`MainService` class, which serves as the main entry point for the application.

🔧 It initializes various services and handles the execution of triggers and workflows.

🔗 The`TriggerService` class handles the interaction between triggers, workflows, and the commit service.

This folder contains files and folders related to a workflow automation system for handling events in the AutoPR system. It includes files for defining data models, handling events, configuring workflows, and executing automation actions. The files define classes and types for messages, threads, issues, pull requests, events, context variables, templates, and executables. Overall, this folder provides a flexible and extensible system for defining and configuring automated actions and workflows in the AutoPR system.

This folder contains a collection of Python files that implement various services and classes for managing and running automated actions in a pull request workflow. These services include the`ActionService` for handling actions, the`CacheService` for caching data, the`CommitService` for managing Git commits, the`DiffService` for working with diffs, the`PlatformService` for interacting with the GitHub platform, the`PublishService` for publishing updates to pull requests, the`TriggerService` for handling triggers and executing workflows, the`Utils` module for formatting and truncating data, and the`WorkflowService` for executing workflows and actions. Each file contains detailed documentation and comments explaining the purpose and functionality of the classes and methods.

📄 This file defines a function called`get_all_triggers`.

📂 It imports necessary modules and classes.

📥 The function takes optional parameters for the configuration directory and repository path.

This folder contains a Python script (`__init__.py`) that collects and loads workflow configurations from YAML files. The script recursively searches for YAML files in a specified folder and its subfolders. It handles exceptions and logs errors during the loading and validation process. The loaded workflows are returned as the result of the`get_all_workflows()` function. The folder also includes several YAML files that define different workflows for tasks such as making API calls and saving responses to files, automating the process of summarizing files and folders, inserting content into files, managing TODO issues in code repositories, and summarizing changes in pull requests.