Trying to make the add_repo_metadata flag to work with Azure Devops

[georgechond94]

Git provider (optional)

Azure

System Info (optional)

No response

Issues details

Hi 👋

I’m trying to enable add_repo_metadata so that PR-Agent picks up and uses our AGENTS.md file located at the root of the repository.

When I run /config, the setting is correctly shown as add_repo_metadata: true. However, based on the logs, this setting does not seem to be applied. The repository metadata (including AGENTS.md) is neither taken into account nor sent to the AI agent.

From the logs, I can only see the default system prompt being sent:

You are PR-Reviewer, a language model designed to review a Git Pull Request (PR).
We are using PR-Agent with webhooks on Azure DevOps, and everything else appears to be working correctly—except for loading and passing the contents of AGENTS.md.

Is your AGENTS.md file in the root of the head branch (the branch being merged)?

Yes it is in the root of the head branch

What is the exact filename and case (AGENTS.md vs AGENTS.MD)?

AGENTS.md

Are you using Azure DevOps webhook or pipeline setup?

Azure DevOps webhook setup

Any guidance on what might be missing or how to debug this further would be appreciated.

Thanks!

[qodo-free-for-open-source-projects]

💡 Auto-generated documentation-based answer:

Based on the documentation, here's what you need to know about the add_repo_metadata feature:

Configuration

The add_repo_metadata feature is configured in the [config] section of your configuration file:

[config]
add_repo_metadata = true

How It Works

When enabled, PR-Agent automatically searches for repository metadata files in your PR's head branch root directory. By default, it looks for:

• AGENTS.MD
• QODO.MD
• CLAUDE.MD

Custom File Names

You can specify custom filenames to search for:

[config]
add_repo_metadata_file_list = ["AGENTS.md", "custom_file.md"]

Troubleshooting Steps

1. Verify file location: Ensure AGENTS.md is in the root directory of your repository's head branch (the branch being merged)

2. Check file name case: The default search is case-sensitive. Make sure your file is named exactly AGENTS.MD (uppercase) or configure add_repo_metadata_file_list with the exact name

3. Configuration file location: For Azure DevOps webhook setup, ensure your configuration is properly set in either:

   • Environment variables (e.g., CONFIG__ADD_REPO_METADATA=true)
   • A .pr_agent.toml file in your repository root
   • Your secrets/configuration file used by the webhook

4. Verify configuration is loaded: Since /config shows the setting correctly, the configuration is being read. The issue might be with file detection or branch context

Additional Information Needed

To provide more specific guidance, it would be helpful to know:

• Is your AGENTS.md file in the root of the head branch (the branch being merged)?
• What is the exact filename and case (AGENTS.md vs AGENTS.MD)?
• Are you using Azure DevOps webhook or pipeline setup?
• Can you share the relevant portion of your configuration file?

Relevant Sources:

• https://docs.qodo.ai/qodo-documentation/qodo-merge/usage-guide/additional_configurations#bringing-additional-repository-metadata-to-qodo-merge
• https://docs.qodo.ai/qodo-documentation/qodo-merge/installation/azure#azure-devops-pipeline
• https://docs.qodo.ai/qodo-documentation/qodo-merge/installation/azure#azure-devops-webhook
• https://docs.qodo.ai/qodo-documentation/qodo-merge/usage-guide/configuration_options