fix links in docs

[even-even]

Hello
In this PR:

1. fix of some links in code
2. fix of some typos in changes files

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

Review Summary by Qodo

Update documentation links and line numbers in configuration references

📝 Documentation

Walkthroughs

Description

• Update GitHub configuration file line number references across documentation
• Fix incorrect line numbers in code comments pointing to configuration.toml
• Correct minor grammar and formatting issues in documentation
• Update section name capitalization from lowercase to uppercase

Diagram

flowchart LR
  A["Documentation Files"] -->|"Update line references"| B["configuration.toml Links"]
  A -->|"Fix grammar/formatting"| C["Documentation Content"]
  B -->|"Reflect actual line positions"| D["Corrected References"]

Loading

File Changes

1. pr_agent/servers/help.py 📝 Documentation +3/-3

Fix configuration file line references in help text

• Update line number references in GitHub configuration file links from L23, L46, L78 to L74, L100,
 L131
• Correct links pointing to pr_reviewer, pr_description, and pr_code_suggestions sections
• Ensure help documentation displays accurate configuration file references

pr_agent/servers/help.py

---

2. docs/docs/tools/help_docs.md 📝 Documentation +2/-2

Update help_docs configuration reference and grammar

• Update configuration file link line number from L199 to L210
• Fix grammar: change "Whether or not to exclude" to "Whether to exclude"

docs/docs/tools/help_docs.md

---

3. docs/docs/tools/similar_issues.md 📝 Documentation +1/-1

Fix similar_issues configuration file line reference

• Update configuration file link line number from L229 to L240 for github_app section

docs/docs/tools/similar_issues.md

---

View more (3)

4. docs/docs/tools/update_changelog.md 📝 Documentation +1/-1

Fix update_changelog configuration file line reference

• Update configuration file link line number from L169 to L180 for pr_update_changelog section

docs/docs/tools/update_changelog.md

---

5. docs/docs/usage-guide/automations_and_usage.md 📝 Documentation +2/-2

Update automations guide configuration references and capitalization

• Update configuration file link line number from L223 to L234 for github_app section
• Change section name capitalization from "github_app" to "GitHub_app"
• Fix grammar: change "yaml" to "YAML" for consistency

docs/docs/usage-guide/automations_and_usage.md

---

6. docs/docs/usage-guide/configuration_options.md 📝 Documentation +1/-1

Fix configuration_options file line reference

• Update configuration file link line number from L66 to L74 for pr_reviewer section

docs/docs/usage-guide/configuration_options.md

---

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

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (1) 📎 Requirement gaps (0) 📐 Spec deviations (0)

1. GitHub_app section name wrong ☑ 📘 Rule violation ✓ Correctness

Description

The docs now refer to the configuration section as GitHub_app, but the actual section name is
github_app. This breaks naming consistency and can mislead users to use a non-existent
configuration section.

Code

docs/docs/usage-guide/automations_and_usage.md[99]

+The [GitHub_app](https://github.com/qodo-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml#L234) section defines GitHub app specific configurations.

Evidence

Compliance requires consistent naming for identifiers; the modified documentation line uses
GitHub_app while the actual configuration section in configuration.toml is [github_app].

Rule 1: Consistent Naming Conventions
docs/docs/usage-guide/automations_and_usage.md[99-99]
pr_agent/settings/configuration.toml[234-234]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The docs reference the GitHub App configuration section as `GitHub_app`, but the actual TOML section name is `[github_app]`.
## Issue Context
This mismatch can confuse users and violates the repository naming consistency expectations.
## Fix Focus Areas
- docs/docs/usage-guide/automations_and_usage.md[99-99]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Review help string over 120 📘 Rule violation ⚙ Maintainability ⭐ New

Description

The modified help message line in get_review_usage_guide() exceeds the repository 120-character
line limit, which can fail Ruff/formatting checks. This is a style compliance violation on newly
changed code.

Code

pr_agent/servers/help.py[28]

+- When commenting, to edit [configurations](https://github.com/Codium-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml#L74) related to the review tool (`pr_reviewer` section), use the following template:

Evidence

PR Compliance ID 8 requires following repository Python style including 120-character lines. The
changed line at pr_agent/servers/help.py:28 is a single long string literal line that clearly
exceeds this limit.

AGENTS.md
pr_agent/servers/help.py[28-28]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
A modified line in `pr_agent/servers/help.py` exceeds the repo's 120-character line-length style requirement.

## Issue Context
The long line is inside user-facing help text. Refactor the Python string construction to keep the rendered output identical while splitting the Python source line(s) to <= 120 chars (e.g., by concatenating multiple shorter string literals within parentheses and keeping the same `\n` placement).

## Fix Focus Areas
- pr_agent/servers/help.py[27-32]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more

Previous review results

Review updated until commit c4618a2

Results up to commit N/A

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0) 📐 Spec deviations (0)

1. GitHub_app section name wrong ☑ 📘 Rule violation ✓ Correctness

Description

The docs now refer to the configuration section as GitHub_app, but the actual section name is
github_app. This breaks naming consistency and can mislead users to use a non-existent
configuration section.

Code

docs/docs/usage-guide/automations_and_usage.md[99]

+The [GitHub_app](https://github.com/qodo-ai/pr-agent/blob/main/pr_agent/settings/configuration.toml#L234) section defines GitHub app specific configurations.

Evidence

Compliance requires consistent naming for identifiers; the modified documentation line uses
GitHub_app while the actual configuration section in configuration.toml is [github_app].

Rule 1: Consistent Naming Conventions
docs/docs/usage-guide/automations_and_usage.md[99-99]
pr_agent/settings/configuration.toml[234-234]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The docs reference the GitHub App configuration section as `GitHub_app`, but the actual TOML section name is `[github_app]`.
## Issue Context
This mismatch can confuse users and violates the repository naming consistency expectations.
## Fix Focus Areas
- docs/docs/usage-guide/automations_and_usage.md[99-99]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

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

Persistent review updated to latest commit c4618a2