chore: add release-candidate in check step

[ferr3ira-gabriel]

Summary by CodeRabbit

• Chores
  • Updated pull request validation workflow to support additional branch types in the development pipeline.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The .github/workflows/check-branch.yml GitHub workflow file was updated to expand branch enforcement rules. The workflow now encompasses three branch types—develop, hotfix, and release-candidate—rather than just develop. The conditional logic was adjusted to exclude these branch prefixes as valid source branches for pull requests. Corresponding user-facing messages, PR review comments, and JSON payloads were updated to reflect the expanded scope of the branch protection policy.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding release-candidate support to the branch enforcement check workflow.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/check_branch_rc

---

📜 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 b3df6a3 and f45983b.

📒 Files selected for processing (1)

• .github/workflows/check-branch.yml (2 hunks)

🔇 Additional comments (2)

.github/workflows/check-branch.yml (2)

1-3: Good documentation updates.

The workflow name and comment clearly reflect the expanded branch enforcement scope.

---

46-62: Conditional logic and messaging are consistent and correct.

The enforcement rule is properly implemented: PRs are rejected unless they originate from develop, release-candidate, or hotfix/* branches. All user-facing messages (echo, JSON payload) accurately reflect the three allowed sources. The pattern matching (exact match for develop/release-candidate; prefix match for hotfix/) aligns with Git Flow conventions.

---

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