Tr/server

[mrT23]

PR Type

Documentation

---

Description

• Updated the GitHub installation guide to include instructions for using specific releases and GitHub Enterprise Server.
• Enhanced local installation documentation to support multiple providers and custom URLs for enterprise instances.
• Revised Qodo Merge Pro installation instructions, clarifying enterprise trial and licensing details.

---

Changes walkthrough 📝

Relevant files

Documentation

github.md Update GitHub installation guide with enterprise server instructions docs/docs/installation/github.md Added instructions for using a specific release with GitHub Actions. Introduced guidance for using the action with GitHub Enterprise Server. Improved formatting and organization of installation instructions. +34/-21  locally.md Enhance local installation guide with multi-provider support docs/docs/installation/locally.md Updated provider options to include multiple platforms. Added instructions for specifying custom URLs for GitHub Enterprise and GitLab instances. Removed redundant instructions for specific Docker image versions. +21/-29  pr_agent_pro.md Revise Qodo Merge Pro installation instructions for enterprise docs/docs/installation/pr_agent_pro.md Clarified installation instructions for GitHub Enterprise Server. Updated trial and licensing information for Qodo Merge Pro. +2/-2

---

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

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

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

🏅 Score: 95

🧪 No relevant tests

🔒 No security concerns identified

🔀 Multiple PR themes Sub-PR theme: Update GitHub installation guide Relevant files: docs/docs/installation/github.md Sub-PR theme: Enhance local installation documentation Relevant files: docs/docs/installation/locally.md Sub-PR theme: Revise Qodo Merge Pro installation instructions Relevant files: docs/docs/installation/pr_agent_pro.md

⚡ Recommended focus areas for review Clarity Improvement The updated text for GitHub Enterprise Server installation is somewhat unclear. It might be beneficial to provide more detailed steps or clarify the process for starting an Enterprise trial.

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Enhancement	✅ Improve the clarity and grammar of instructions for using Qodo Merge Pro on GitHub Enterprise Server Suggestion Impact: The suggestion improved the grammatical structure of the sentence by changing "To using" to "To use". code diff: -To using Qodo Merge Pro application on your private GitHub Enterprise Server, you will need to contact us for starting an [Enterprise](https://www.codium.ai/pricing/) trial. +To use Qodo Merge Pro application on your private GitHub Enterprise Server, you will need to contact us for starting an [Enterprise](https://www.codium.ai/pricing/) trial. The sentence structure in the new instructions for GitHub Enterprise Server could be improved for clarity. Consider rephrasing to make it more straightforward and grammatically correct. docs/docs/installation/pr_agent_pro.md [21] -To using Qodo Merge Pro application on your private GitHub Enterprise Server, you will need to contact us for starting an [Enterprise](https://www.codium.ai/pricing/) trial. +To use the Qodo Merge Pro application on your private GitHub Enterprise Server, you will need to contact us to start an [Enterprise](https://www.codium.ai/pricing/) trial. Apply this suggestion Suggestion importance[1-10]: 7 Why: The suggestion enhances the clarity and grammatical correctness of the instructions, making them easier to understand. This is important for user comprehension, especially in installation guides, but it is not critical to the functionality of the documentation.	7
	Standardize the format of environment variable placeholders for consistency Consider using a consistent format for environment variable placeholders. Currently, some use angle brackets (<>) while others use dollar signs ($). Standardizing to one format, preferably angle brackets, would improve readability and consistency. docs/docs/installation/locally.md [56-66] docker run --rm -it -e OPENAI.KEY=<your key> -e CONFIG.GIT_PROVIDER=gitlab -e GITLAB.PERSONAL_ACCESS_TOKEN=<your token> codiumai/pr-agent:latest --pr_url <pr_url> review ... -docker run --rm -it -e CONFIG.GIT_PROVIDER=bitbucket -e OPENAI.KEY=$OPENAI_API_KEY -e BITBUCKET.BEARER_TOKEN=$BITBUCKET_BEARER_TOKEN codiumai/pr-agent:latest --pr_url=<pr_url> review +docker run --rm -it -e CONFIG.GIT_PROVIDER=bitbucket -e OPENAI.KEY=<your key> -e BITBUCKET.BEARER_TOKEN=<your token> codiumai/pr-agent:latest --pr_url=<pr_url> review Suggestion importance[1-10]: 5 Why: The suggestion to standardize the format of environment variable placeholders improves readability and consistency, which is beneficial for documentation. However, it is a minor enhancement and does not affect the functionality of the code.	5

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

💡 Need additional feedback ? start a PR chat