Document an example on how to configure PR Agent using environment variables

[addianto]

User description

This PR adds a short documentation on how to configure PR Agent using environment variables.

Resolves #1398.

---

PR Type

Documentation

---

Description

• Added comprehensive documentation about configuring PR Agent using environment variables
• Explained the Dynaconf configuration system and its environment variable convention (<TABLE>__<KEY>=<VALUE>)
• Provided practical example for GitLab setup using .env file
• Added Docker command example showing how to use environment variables file
• Improved clarity of configuration instructions for self-hosted instances

---

Changes walkthrough 📝

	Relevant files
Documentation	locally.md Document environment variables configuration with Dynaconf docs/docs/installation/locally.md Added explanation about using Dynaconf for configuration management Added example of using environment variables for configuration Included sample .env file content for GitLab setup Added Docker command example using env-file +22/-1

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[qodo-merge-pro-for-open-source]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis ✅ 1398 - Fully compliant Compliant requirements: Improve documentation for configuring PR Agent using environment variables Explain that configuration is managed using Dynaconf Provide examples of how to override local configuration using environment variables Focus on Docker container configuration use case

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🏅 Score: 95

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

[qodo-merge-pro-for-open-source]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Security	✅ Add security warning about protecting sensitive credentials in environment files Suggestion Impact: Added a security warning about not committing .env files to version control, though with slightly different wording than suggested code diff: +> Warning: Never commit the `.env` file to version control system as it might contains sensitive credentials! Add a security warning about not committing the .env file to version control, and recommend adding it to .gitignore to prevent accidental exposure of sensitive credentials. docs/docs/installation/locally.md [77-84] You can define the environment variables in a plain text file named `.env` with the following content: CONFIG__GIT_PROVIDER="gitlab" GITLAB__URL="" GITLAB__PERSONAL_ACCESS_TOKEN="" OPENAI__KEY="" +> ⚠️ **Security Warning**: Never commit the `.env` file to version control as it contains sensitive credentials. Add `.env` to your `.gitignore` file to prevent accidental exposure. + Apply this suggestion Suggestion importance[1-10]: 9 Why: This is a critical security suggestion that helps prevent accidental exposure of sensitive credentials. Adding a warning about not committing .env files is essential for maintaining security best practices, especially given that the file contains API tokens and access credentials.	9

• Author self-review: I have reviewed the PR code suggestions, and addressed the relevant ones.

[addianto]

PR Code Suggestions ✨

Explore these optional code suggestions:
Category Suggestion Score
Security
✅ Add security warning about protecting sensitive credentials in environment files

9

* [ ]   **Author self-review**: I have reviewed the PR code suggestions, and addressed the relevant ones.

I have tried to address the suggestion in b88507a and 1167694.

[mrT23]

thanks fo the PR 👍

[addianto]

You're welcome. Cheers. 😄