assigning tickets to rovo cli?

[M]

 
How do I give Rovo CLI GitHub access and automate the full “ticket → branch → PR” workflow?

---

Context
I’m experimenting with Rovo CLI (acli rovodev) on top of Atlassian CLI. It already reads a Jira ticket and understands the work to do, but I’m unsure how to wire it into GitHub and make the whole process repeatable.

What I’d like to achieve

1. GitHub authentication
   Rovo should be able to pull main and push feature branches / PRs.
   I got this working once by accident—no idea which token or flag actually made it succeed.

2. Reusable “system prompt” / script
   When a ticket is assigned, I want Rovo to automatically:

   • Move the issue to In Progress

   • Add a “Started work, pulling source” comment

   • git pull from main to ensure local is current

   • Create a branch named after the Jira key

   • Make the code changes & tests

   • Commit and push the branch

3. Where to store that prompt
   Should this live in a markdown file at the repo root (e.g., rovo_workflow.md) or is there a better place?

Questions

• What’s the correct way to grant/refresh GitHub credentials for Rovo CLI?

• Is there an official pattern for supplying a workflow prompt or config file?

• Any sample repos or docs that show the end-to-end setup?

Thanks for any guidance!

[Jovana Dunisijevic]

Hey @M 

These are all good questions!

I've tried braking it down for you:

1. GitHub Authentication

• Rovo CLI uses your local GitHub credentials. For best results, install the GitHub CLI and authenticate with gh auth login before using Rovo CLI. This ensures Rovo Dev can pull from main and push branches/PRs as you.
• If you run into issues, check that your GitHub token has the right scopes (repo, workflow) and is active. You can refresh credentials by re-running gh auth login or updating your token.

2. Reusable Workflow Prompt / Script

• Automating the full flow: Rovo CLI can automate moving Jira issues, commenting, pulling from main, creating branches, making changes, and opening PRs. You can define these steps as a reusable prompt or instruction set.
• Best practice: Break down large tasks into smaller steps (e.g., create the branch first, then make incremental changes). This improves reliability and avoids timeouts.

3. Where to Store the Prompt

• Repo-level memory: Place your workflow prompt in a .agent.local.md file at the root of your repo. This file acts as persistent “memory” for Rovo Dev and is not checked into Git, so it’s local to your machine.
• User-level memory: For global prompts, use ~/.rovodev/.agent.md.

4. Granting/Refreshing GitHub Credentials

• Install and authenticate GitHub CLI (gh auth login).
• Ensure Rovo CLI is configured to use the GitHub MCP server (see acli rovodev mcp).
• If you change tokens, re-authenticate with GitHub CLI.

5. Supplying Workflow Prompts/Config

• Use .agent.local.md in your repo root for repo-specific instructions.
• Use ~/.rovodev/.agent.md for user-wide instructions.
• You can also use /memory init in interactive mode to generate and customize these files.

6. Sample Repos or Docs

• While there isn’t a public sample repo yet, you can find best practices and example workflows in the user guide: https://community.atlassian.com/forums/Rovo-for-Software-Teams-Beta/Rovo-Dev-CLI-Prompt-and-Usage-Guide/ba-p/3047073
• For advanced automation (e.g., triggering agents from Jira), see https://community.atlassian.com/forums/Rovo-for-Software-Teams-Beta/30-PRs-in-30-Minutes-Automating-Route-Migrations-with-Rovo-Dev/ba-p/3035999

I hope this helps!

Let us know if you have more questions!

Kindest regards,

Jovana