Add publish_output_progress config support to AzureDevOps, BitBucket and Gitlab providers

[pdecat]

PR Type

enhancement

---

Description

• Added support for the publish_output_progress configuration in AzureDevOps, BitBucket, and GitLab providers.
• Implemented a condition to skip publishing temporary comments if the publish_output_progress setting is disabled.
• Enhanced logging to provide debug information when temporary comments are skipped.

---

Changes walkthrough 📝

Relevant files

Enhancement

azuredevops_provider.py Add conditional logic for temporary comment publishing      pr_agent/git_providers/azuredevops_provider.py Added a condition to skip publishing temporary comments based on configuration. Introduced logging for skipped temporary comments. +3/-0      bitbucket_provider.py Add conditional logic for temporary comment publishing      pr_agent/git_providers/bitbucket_provider.py Added a condition to skip publishing temporary comments based on configuration. Introduced logging for skipped temporary comments. +3/-0      gitlab_provider.py Add conditional logic for temporary comment publishing      pr_agent/git_providers/gitlab_provider.py Added a condition to skip publishing temporary comments based on configuration. Introduced logging for skipped temporary comments. +3/-0

---

💡 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:

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

🏅 Score: 95

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Error Handling Verify that skipping temporary comments doesn't affect error handling or cause any side effects in the Azure DevOps integration Return Value Validate that returning None when skipping temporary comments is handled properly by calling code

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

PR Code Suggestions ✨

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

---

Previous suggestions

Suggestions up to commit a825aec

Category	Suggestion	Score
Qodo best practice	Move string literals to constants to improve maintainability and reduce duplication Define a constant for the debug log message to maintain consistency and make future updates easier. pr_agent/git_providers/azuredevops_provider.py [382] -get_logger().debug(f"Skipping publish_comment for temporary comment: {pr_comment}") +SKIP_TEMP_COMMENT_MSG = "Skipping publish_comment for temporary comment: {comment}" +get_logger().debug(SKIP_TEMP_COMMENT_MSG.format(comment=pr_comment)) Suggestion importance[1-10]: 3 Why: While the suggestion to extract the debug message into a constant is valid for code maintainability, its impact is minimal since this is a simple debug log message that appears in multiple provider files and would require coordinated changes across all of them.	3

[pdecat]

/help

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

PR Agent Walkthrough 🤖

Welcome to the PR Agent, an AI-powered tool for automated pull request analysis, feedback, suggestions and more.

Here is a list of tools you can use to interact with the PR Agent:

Tool	Description	Trigger Interactively 💎
DESCRIBE	Generates PR description - title, type, summary, code walkthrough and labels	Run
REVIEW	Adjustable feedback about the PR, possible issues, security concerns, review effort and more	Run
IMPROVE	Code suggestions for improving the PR	Run
UPDATE CHANGELOG	Automatically updates the changelog	Run
ADD DOCS 💎	Generates documentation to methods/functions/classes that changed in the PR	Run
TEST 💎	Generates unit tests for a specific component, based on the PR code change	Run
IMPROVE COMPONENT 💎	Code suggestions for a specific component that changed in the PR	Run
ANALYZE 💎	Identifies code components that changed in the PR, and enables to interactively generate tests, docs, and code suggestions for each component	Run
ASK	Answering free-text questions about the PR	[*]
GENERATE CUSTOM LABELS 💎	Generates custom labels for the PR, based on specific guidelines defined by the user	[*]
CI FEEDBACK 💎	Generates feedback and analysis for a failed CI job	[*]
CUSTOM PROMPT 💎	Generates custom suggestions for improving the PR code, derived only from a specific guidelines prompt defined by the user	[*]
SIMILAR ISSUE	Automatically retrieves and presents similar issues	[*]

(1) Note that each tool be triggered automatically when a new PR is opened, or called manually by commenting on a PR.

(2) Tools marked with [*] require additional parameters to be passed. For example, to invoke the /ask tool, you need to comment on a PR: /ask "<question content>". See the relevant documentation for each tool for more details.

[pdecat]

This is copied from https://github.com/Codium-ai/pr-agent/blob/eb0c959ca9767d506fc7be4303fe5e73a80de882/pr_agent/git_providers/github_provider.py#L281

[mrT23]

cool, thanks