docs: add CI trigger map for GitHub Actions workflows

[diegolmello]

Proposed changes

Adds a single source of truth for CI visibility. Until now there was no document mapping GitHub Actions triggers to workflows — answering "what runs on a PR?" or "what runs on a push to develop?" meant opening and cross-referencing several of the 12 workflow files, plus the GitHub UI for the approval gates.

This PR adds .github/README.md with three sections:

• Entrypoints — the 4 event-triggered workflows, their trigger event, and a one-line summary of what each runs.
• Call graph — a Mermaid diagram of entrypoint workflows → reusable workflows → composite actions.
• Manual gates — the 4 GitHub environment approval gates and the condition under which each fires (these previously lived only in the GitHub UI).

It also adds a short Continuous Integration section to CLAUDE.md pointing to the map.

Scope is deliberately limited to cross-file facts that are not present in any single workflow file (the call graph, the gates, the entrypoint overview), so the document stays low-drift. Per-workflow on:/branch/path details remain in the YAML as the source of truth. No workflow or action YAML is modified, so check contexts and branch protection are unaffected.

Issue(s)

https://rocketchat.atlassian.net/browse/NATIVE-1343

How to test or reproduce

• Open .github/README.md on GitHub and confirm the Mermaid call graph renders and the workflow links resolve.
• Confirm the entrypoints, call graph, and gates match the current workflow files under .github/workflows/.

Screenshots

N/A — documentation only.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• Improvement (non-breaking change which improves a current function)
• New feature (non-breaking change which adds functionality)
• Documentation update (if none of the other choices apply)

Checklist

• I have read the CONTRIBUTING doc
• I have signed the CLA
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works (if applicable)
• I have added necessary documentation (if applicable)
• Any dependent changes have been merged and published in downstream modules

Further comments

The document intentionally covers only facts that span multiple files. If it begins to drift from the workflows, a natural follow-up is to generate it from the workflow YAML and fail CI when the checked-in copy is stale.

https://claude.ai/code/session_013Ai5iqwADTryxoiJRNdhCa

Summary by CodeRabbit

• Documentation
  • Added a CI overview page explaining how major GitHub events map to workflows, including a visual call graph and manual gate conditions.
  • Updated the main project guidance with a new “Continuous Integration” section that directs readers to the CI overview for trigger, call graph, and gate details.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 57742b90-7bf1-4bd7-9f46-3e0a273d23b5

📥 Commits

Reviewing files that changed from the base of the PR and between 2e2eeef and 864cbc4.

📒 Files selected for processing (2)

• .github/README.md
• CLAUDE.md

---

Walkthrough

Added CI reference documentation in .github/README.md covering workflow entrypoints, reusable workflow relationships, and manual gate conditions. CLAUDE.md now links to that CI reference.

Changes

Continuous integration documentation

Layer / File(s)	Summary
CI reference page and pointer .github/README.md, CLAUDE.md	.github/README.md adds CI entrypoints, a call graph, and manual gates; CLAUDE.md adds a pointer to that documentation.

Estimated code review effort: 1 (Trivial) | ~4 minutes

Suggested labels: type: chore

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the documentation change adding a CI trigger map for GitHub Actions workflows.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (1)

• NATIVE-1343: Request failed with status code 401

---

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.}

[OtavioStasiak]

LGTM