Refine welcome message

[koppor]

User description

Follow-up to #14351

Mandatory checks

• I own the copyright of the code submitted and I license it under the MIT license
• [/] I manually tested my changes in running JabRef (always required)
• [/] I added JUnit tests for changes (if applicable)
• [/] I added screenshots in the PR description (if change is visible to the user)
• [/] I described the change in CHANGELOG.md in a way that is understandable for the average user (if change is visible to the user)
• [/] I checked the user documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request updating file(s) in https://github.com/JabRef/user-documentation/tree/main/en.

---

PR Type

Documentation

---

Description

• Refine welcome message for new pull requests

• Add information about Qodo review assistance tool

• Link to contribution guide in PR message

• Simplify AI Usage Policy reference text

---

Diagram Walkthrough

flowchart LR
  A["PR opened workflow"] -- "Update message" --> B["Add Qodo info"]
  A -- "Update message" --> C["Link contribution guide"]
  A -- "Update message" --> D["Simplify AI policy text"]

Loading

File Walkthrough

	Relevant files
Documentation	on-pr-opened.yml Update PR welcome message with Qodo and guide links            .github/workflows/on-pr-opened.yml Added information about Qodo tool for review assistance Added link to contribution guide in the PR message Simplified the AI Usage Policy reference by removing redundant text about contribution guide Fixed typo: "assitance" and "upate" (note: these appear to be typos in the PR) +4/-1

---

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

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

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

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	✅ Correct typos in the welcome message Suggestion Impact: The commit directly implements the suggestion by fixing both typos in lines 5 and 6 of the diff, changing "assitance" to "assistance" and "upate" to "update" code diff: - We also use [Qodo](https://www.qodo.ai/) for review assitance. - It will upate your pull request description with a review help and offer suggestions to improve the pull request. + We also use [Qodo](https://www.qodo.ai/) for review assistance. + It will update your pull request description with a review help and offer suggestions to improve the pull request. Correct the typos "assitance" to "assistance" and "upate" to "update" in the automated welcome message. .github/workflows/on-pr-opened.yml [26-27] -We also use [Qodo](https://www.qodo.ai/) for review assitance. -It will upate your pull request description with a review help and offer suggestions to improve the pull request. +We also use [Qodo](https://www.qodo.ai/) for review assistance. +It will update your pull request description with a review help and offer suggestions to improve the pull request. [Suggestion processed] Suggestion importance[1-10]: 4 __ Why: The suggestion correctly identifies and fixes two typos (assitance and upate) in the newly added text, which improves the professionalism of the automated message.	Low
Update

[subhramit]

Is there a way for the review help to be a comment instead of appending to PR desc?
I would prefer if any work submitted by the contributor remains untouched, but more of a nitpick

[koppor]

No and I agree.