Update atlassian-connect.json

[mrT23]

PR Type

enhancement, configuration changes

---

Description

• Enhanced the scopes in atlassian-connect.json to provide additional permissions.
• Updated scopes to include repository:write, pullrequest:write, and wiki for improved functionality.

---

Changes walkthrough 📝

	Relevant files
Configuration changes	atlassian-connect.json Update scopes and permissions in atlassian-connect.json    pr_agent/servers/atlassian-connect.json Updated scopes to include repository:write, pullrequest:write, and wiki. Enhanced permissions for repository and pull request operations. Added new scope for wiki access. +4/-3

---

💡 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

🔒 Security concerns Elevated permissions: The PR introduces new scopes (repository:write, pullrequest:write, and wiki) which grant more permissions to the application. While this may be necessary for enhanced functionality, it also increases the potential impact if the application is compromised. Ensure that these elevated permissions are absolutely necessary and that proper security measures are in place to protect against unauthorized access or misuse.

🔀 No multiple PR themes

⚡ Recommended focus areas for review Permission Scope Verify if the added scopes (repository:write, pullrequest:write, and wiki) are necessary and align with the principle of least privilege.

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Best practice	Specify individual webhook events for more precise control over event handling Consider adding more specific webhook events instead of using the wildcard "*". This allows for more granular control over which events trigger the webhook. pr_agent/servers/atlassian-connect.json [27-31] "webhooks": [ { - "event": "*", + "event": "repo:push", + "url": "/webhook" + }, + { + "event": "pr:opened", + "url": "/webhook" + }, + { + "event": "pr:merged", "url": "/webhook" } ] Apply this suggestion Suggestion importance[1-10]: 7 Why: This suggestion improves the granularity of webhook event handling by specifying individual events instead of using a wildcard. It enhances control and security, making it a valuable improvement.	7
Enhancement	Include a version field in the JSON configuration for better change tracking and compatibility management Consider adding a version field to the JSON file to track changes and ensure compatibility with future updates. pr_agent/servers/atlassian-connect.json [8-11] { + "version": "1.0.0", "key": "pr-agent", "name": "PR Agent", "description": "A Bitbucket app for PR Agent", Apply this suggestion Suggestion importance[1-10]: 6 Why: Adding a version field is a good practice for tracking changes and ensuring compatibility with future updates. This suggestion enhances maintainability and version control of the configuration file.	6

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

💡 Need additional feedback ? start a PR chat

[mrT23]

Question:

how to turn off all automatic tools on gitlab ?

Answer:

To turn off all automatic tools on GitLab, you need to set the pr_commands parameter to an empty list in the configuration file. This will cancel the automatic run of all tools when a new PR is opened.

Relevant Sources:

• https://qodo-merge-docs.qodo.ai/usage-guide/automations_and_usage#gitlab-webhook
• https://qodo-merge-docs.qodo.ai/usage-guide/automations_and_usage#github-app

[mrT23]

Question:

how to get more customized code suggestions ?

Answer:

To get more customized code suggestions, you can use the extra_instructions configuration option to provide specific guidance to the AI model. Additionally, creating a best_practices.md wiki page with tailored coding standards and guidelines for your repo can help the AI model generate suggestions that adhere to your organization's best practices.

Here are examples of how to use these features:

1. Extra Instructions:
   You can add specific instructions for the AI model in the improve tool's configuration:

   [pr_code_suggestions]
   extra_instructions="""\
   (1) Focus on memory optimization
   (2) Avoid using global variables
   """

2. Best Practices:
   Create a best_practices.md wiki page in your repository with detailed coding standards and guidelines. The AI model will reference this page to ensure the suggestions comply with your organization's best practices.

For more details on setting these configurations, refer to the documentation sections on extra instructions and best practices.

Relevant Sources:

• https://qodo-merge-docs.qodo.ai/tools/improve#extra-instructions-and-best-practices
• https://qodo-merge-docs.qodo.ai/usage-guide/configuration_options#wiki-configuration-file-💎

[mrT23]

Question:

how to get more customized code suggestions ?

Answer:

To get more customized code suggestions, you can use the extra_instructions and best_practices configuration options with the improve tool. These options allow you to guide the AI model to generate more tailored suggestions based on specific instructions or coding standards relevant to your project.

For extra_instructions, you can specify detailed guidance directly in the command or configuration file. For example:

[pr_code_suggestions]
extra_instructions="""\
(1) Focus on security improvements
(2) Avoid suggestions to refactor large functions unless necessary
(3) Prioritize performance optimizations
"""

For best_practices, you can create a dedicated wiki page called best_practices.md in your repository, which contains a list of coding standards and guidelines. The AI model will use this page as a reference to generate suggestions that align with your project's best practices.

Additionally, you can use the custom_prompt tool to generate suggestions based on custom prompts that define specific guidelines or focus areas for the suggestions.

Relevant Sources:

• https://qodo-merge-docs.qodo.ai/tools/improve#extra-instructions-and-best-practices
• https://qodo-merge-docs.qodo.ai/tools/custom_prompt#overview