chore: update .gitignore

[javier-godoy]

Summary by CodeRabbit

• Chores
  • Updated version control ignore patterns to exclude generated frontend assets and build outputs from the repository.

[coderabbitai]

Walkthrough

Adds three new ignore patterns to .gitignore to exclude generated frontend assets and bundled files from version control: /src/main/frontend/generated, /src/main/frontend/index.html, and /src/main/bundles.

Changes

Cohort / File(s)	Summary
Git configuration .gitignore	Adds three ignore patterns for generated frontend artifacts and bundle files

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The pull request title "chore: update .gitignore" is directly related to the changeset, which adds three new ignore patterns to the .gitignore file. The title clearly identifies the file being modified and the action being performed. While the word "update" is somewhat generic, it is specific enough when paired with ".gitignore" to convey meaningful information about the change. A teammate scanning the commit history would clearly understand that .gitignore was modified in this PR.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch gitignore

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9968462 and 58ca874.

📒 Files selected for processing (1)

• .gitignore (1 hunks)

🔇 Additional comments (1)

.gitignore (1)

15-17: LGTM!

The three new patterns are syntactically correct, appropriately scoped to the repository root using leading /, and specifically target generated frontend assets and bundled files without risk of over-matching. The changes align well with the project's build structure and follow the existing style conventions in the file.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

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 SonarQube Cloud

[mlopezFC]

LGTM