Enhance pull request metadata handling in comments.php

[guibranco]

Description

• Enhanced the handling of pull request metadata by decoding the JSON response from the GitHub API.
• Updated the headRef and headSha in the metadata for better tracking of pull request details.

---

Changes walkthrough 📝

	Relevant files
Enhancement	comments.php Enhance pull request metadata handling                                      src/comments.php Added a line to decode the JSON response from GitHub API. Updated the metadata with the pull request's head reference and SHA. +1/-0

[penify-dev[bot]]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	2, because the changes are straightforward and involve a single file with a small addition.
🧪 Relevant tests	No
⚡ Possible issues	No
🔒 Security concerns	No

[deepsource-io[bot]]

Here's the code health analysis summary for commits be03b00..da7704c. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
Docker	✅ Success		View Check ↗
PHP	✅ Success		View Check ↗
Secrets	✅ Success		View Check ↗
SQL	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[penify-dev[bot]]

PR Code Suggestions ✨

Category	Suggestion	Score
Possible bug	Add error handling for JSON decoding to ensure robustness ___ **Ensure that the JSON decoding is successful by checking for errors after calling json_decode, as it may fail and return null.** [Src/comments.php [520]](https://github.com/guibranco/gstraccini-bot/pull/494/files#diff-c016a4b724b06cf94f3e5e764ca4f4eb4d42b550ddca3566f9b03c2f3bec51faR520-R520) ```diff $pullRequest = json_decode($pullRequestResponse->body); +if (json_last_error() !== JSON_ERROR_NONE) { + return false; // or handle the error appropriately +} ``` Suggestion importance[1-10]: 9 Why: This suggestion addresses a potential bug by ensuring that JSON decoding is successful, which is crucial for the stability of the function.	9
	Validate the existence of properties in the decoded JSON before accessing them ___ **Consider validating that the head property exists in the decoded JSON object before accessing head->ref to avoid potential errors.** [Src/comments.php [522]](https://github.com/guibranco/gstraccini-bot/pull/494/files#diff-c016a4b724b06cf94f3e5e764ca4f4eb4d42b550ddca3566f9b03c2f3bec51faR522-R522) ```diff -$metadata["headRef"] = $pullRequest->head->ref; +if (isset($pullRequest->head) && isset($pullRequest->head->ref)) { + $metadata["headRef"] = $pullRequest->head->ref; +} else { + return false; // or handle the error appropriately +} ``` Suggestion importance[1-10]: 9 Why: This suggestion prevents potential errors by validating the existence of properties in the decoded JSON, which is essential for robust code.	9
Maintainability	Rename the variable to enhance clarity and maintainability ___ **Consider using a more descriptive variable name for $pullRequest to clarify its purpose and improve code readability.** [Src/comments.php [520]](https://github.com/guibranco/gstraccini-bot/pull/494/files#diff-c016a4b724b06cf94f3e5e764ca4f4eb4d42b550ddca3566f9b03c2f3bec51faR520-R520) ```diff -$pullRequest = json_decode($pullRequestResponse->body); +$decodedPullRequest = json_decode($pullRequestResponse->body); ``` Suggestion importance[1-10]: 6 Why: This suggestion enhances code readability by proposing a more descriptive variable name, which is beneficial but not critical.	6
	Eliminate unnecessary whitespace for cleaner code ___ **Remove the extra newline added at line 519 for better code readability and consistency.** [Src/comments.php [519]](https://github.com/guibranco/gstraccini-bot/pull/494/files#diff-c016a4b724b06cf94f3e5e764ca4f4eb4d42b550ddca3566f9b03c2f3bec51faR519-R519) ```diff +return false; - ``` Suggestion importance[1-10]: 3 Why: While this suggestion improves code style, it addresses a minor issue that does not significantly impact functionality.	3

[github-actions[bot]]

Infisical secrets check: :white_check_mark: No secrets leaked!

Scan results:

4:07AM INF scanning for exposed secrets...
4:07AM INF 431 commits scanned.
4:07AM INF scan completed in 117ms
4:07AM INF no leaks found

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud