Update git configuration in prettier.yml

[guibranco]

Description

• Enhanced the git configuration in the prettier.yml workflow.
• Changed the user email to a specific static email for better traceability.

---

Changes walkthrough 📝

	Relevant files
Configuration changes	prettier.yml Update git configuration in prettier.yml                                  .github/workflows/prettier.yml Updated the email configuration for git. Changed the email from a dynamic value to a static one. +1/-2

[penify-dev[bot]]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	2, because the changes are straightforward and involve a simple configuration update with minimal complexity.
🧪 Relevant tests	No
⚡ Possible issues	No
🔒 Security concerns	No

[penify-dev[bot]]

PR Code Suggestions ✨

Category	Suggestion	Score
Performance	Add a conditional check to execute git configuration only when necessary ___ **Consider adding a conditional check to ensure that the git configuration commands are only executed if the previous step indicates that files have changed, to avoid unnecessary configuration.** [.github/workflows/prettier.yml [118]](https://github.com/guibranco/gstraccini-bot/pull/461/files#diff-f4594992f4599bbb2b28080456c07ec027f0c29b2e5d34c0ef0c8bac6f539b9bR118-R118) ```diff -git config --local user.email "150967461+gstraccini[bot]@users.noreply.github.com" +if [ "${{ steps.verify-changed-files.outputs.files_changed }}" == 'true' ]; then + git config --local user.email "150967461+gstraccini[bot]@users.noreply.github.com" +fi ``` Suggestion importance[1-10]: 8 Why: Adding a conditional check would prevent unnecessary execution of commands, improving performance and efficiency.	8
Maintainability	Use environment variables for the user email configuration ___ **Consider using environment variables for the user email to enhance flexibility and maintainability, allowing for easier updates in different environments.** [.github/workflows/prettier.yml [118]](https://github.com/guibranco/gstraccini-bot/pull/461/files#diff-f4594992f4599bbb2b28080456c07ec027f0c29b2e5d34c0ef0c8bac6f539b9bR118-R118) ```diff -git config --local user.email "150967461+gstraccini[bot]@users.noreply.github.com" +git config --local user.email "${{ secrets.GIT_USER_EMAIL }}" ``` Suggestion importance[1-10]: 7 Why: Using environment variables for configuration improves maintainability, but the current email format is valid and functional as is.	7
Best practice	Change the user name configuration to global for consistency ___ **It is advisable to use --global for the user name configuration to ensure consistency across all repositories for the bot user.** [.github/workflows/prettier.yml [119]](https://github.com/guibranco/gstraccini-bot/pull/461/files#diff-f4594992f4599bbb2b28080456c07ec027f0c29b2e5d34c0ef0c8bac6f539b9bR119-R119) ```diff -git config --local user.name "gstraccini[bot]" +git config --global user.name "gstraccini[bot]" ``` Suggestion importance[1-10]: 6 Why: Changing to global configuration for the user name can enhance consistency, but the local setting may be appropriate depending on the context.	6
	Validate the email format used in the git configuration ___ **Ensure that the email format is valid and follows the standard email conventions to prevent potential issues with git operations.** [.github/workflows/prettier.yml [118]](https://github.com/guibranco/gstraccini-bot/pull/461/files#diff-f4594992f4599bbb2b28080456c07ec027f0c29b2e5d34c0ef0c8bac6f539b9bR118-R118) ```diff -git config --local user.email "150967461+gstraccini[bot]@users.noreply.github.com" +git config --local user.email "gstraccini[bot]@users.noreply.github.com" ``` Suggestion importance[1-10]: 5 Why: The email format is already valid, but the suggestion to validate it further is reasonable for best practices.	5

[deepsource-io[bot]]

Here's the code health analysis summary for commits 63f681a..6a09c22. 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.

[github-actions[bot]]

Infisical secrets check: :white_check_mark: No secrets leaked!

Scan results:

6:20PM INF scanning for exposed secrets...
6:20PM INF 404 commits scanned.
6:20PM INF scan completed in 120ms
6:20PM 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