OpenHands/docs/modules/usage/how-to/github-action.md

Using the OpenHands GitHub Action

This guide explains how to use the OpenHands GitHub Action, both within the OpenHands repository and in your own projects.

Using the Action in the OpenHands Repository

To use the OpenHands GitHub Action in a repository, you can:

1. Create an issue in the repository.
2. Add the fix-me label to the issue or leave a comment on the issue starting with @openhands-agent.

The action will automatically trigger and attempt to resolve the issue.

Installing the Action in a New Repository

To install the OpenHands GitHub Action in your own repository, follow the README for the OpenHands Resolver.

Usage Tips

Iterative resolution

1. Create an issue in the repository.
2. Add the fix-me label to the issue, or leave a comment starting with @openhands-agent
3. Review the attempt to resolve the issue by checking the pull request
4. Follow up with feedback through general comments, review comments, or inline thread comments
5. Add the fix-me label to the pull request, or address a specific comment by starting with @openhands-agent

Label versus Macro

• Label (fix-me): Requests OpenHands to address the entire issue or pull request.
• Macro (@openhands-agent): Requests OpenHands to consider only the issue/pull request description and the specific comment.

Advanced Settings

Add custom repository settings

You can provide custom directions for OpenHands by following the README for the resolver.

Configure custom macro

To customize the default macro (@openhands-agent):

1. Create a repository variable named OPENHANDS_MACRO
2. Assign the variable a custom value

Writing Effective .openhands_instructions Files

The .openhands_instructions file is a file that you can put in the root directory of your repository to guide OpenHands in understanding and working with your repository effectively. Here are key tips for writing high-quality instructions:

Core Principles

1. Concise but Informative: Provide a clear, focused overview of the repository that emphasizes the most common actions OpenHands will need to perform.

2. Repository Structure: Explain the key directories and their purposes, especially highlighting where different types of code (e.g., frontend, backend) are located.

3. Development Workflows: Document the essential commands for:

   • Building and setting up the project
   • Running tests
   • Linting and code quality checks
   • Any environment-specific requirements

4. Testing Guidelines: Specify:

   • Where tests are located
   • How to run specific test suites
   • Any testing conventions or requirements

Example Structure

# Repository Overview
[Brief description of the project]

## General Setup
- Main build command
- Development environment setup
- Pre-commit checks

## Backend
- Location and structure
- Testing instructions
- Environment requirements

## Frontend
- Setup prerequisites
- Build and test commands
- Environment variables

## Additional Guidelines
- Code style requirements
- Special considerations
- Common workflows

For a real-world example, refer to the OpenHands repository's .openhands_instructions.