GitHub Issues

When you include a GitHub issue URL in your Slack message, Ryven reads the full issue and uses it as context for the task.

How it works

1. Ryven detects GitHub issue URLs in your message using pattern matching
2. It fetches the issue details via the GitHub API:
   • Issue title
   • Issue body (description)
   • All comments
3. This context is included in the agent's prompt alongside your task description

Example

@ryven Fix the login redirect bug described in https://github.com/acme/web-app/issues/87

Ryven will:

1. Fetch issue #87 from acme/web-app
2. Read the bug description and any discussion in the comments
3. Auto-select web-app as the target repository
4. Start the task with full issue context

Auto-detection

The repository is automatically detected from the issue URL. You don't need to specify the repo name separately when linking an issue.

If the repo in the issue URL isn't connected to your workspace, Ryven will let you know in the Slack thread.

PR linking

When Ryven opens a pull request for the task, the PR body includes:

• A summary of the task
• A reference to the linked issue
• A link back to the Slack thread

This gives reviewers full traceability from the PR back to the original request and issue.

Multiple issues

You can include multiple issue URLs in a single message. Ryven reads all of them and includes the combined context. However, the target repository is determined from the first issue URL found.