Skip to content

Add @jsx common parser issues in the docs#123

Merged
vjeux merged 1 commit intofacebook:masterfrom
vjeux:patch-2
Jun 28, 2013
Merged

Add @jsx common parser issues in the docs#123
vjeux merged 1 commit intofacebook:masterfrom
vjeux:patch-2

Conversation

@vjeux
Copy link
Copy Markdown
Contributor

@vjeux vjeux commented Jun 24, 2013

No description provided.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

without transforming it

Update getting-started.md
vjeux added a commit that referenced this pull request Jun 28, 2013
Add @jsx common parser issues in the docs
@vjeux vjeux merged commit 811df48 into facebook:master Jun 28, 2013
bvaughn added a commit to bvaughn/react that referenced this pull request Aug 13, 2019
Picking a DOM node focuses the tree
taneliang referenced this pull request in MLH-Fellowship/react Aug 17, 2020
taneliang referenced this pull request in MLH-Fellowship/react Aug 19, 2020
@ElijahOsazuwa

This comment was marked as spam.

@ElijahOsazuwa

This comment was marked as spam.

@JankoD84
Copy link
Copy Markdown

JankoD84 commented Apr 5, 2026

Dulvarn PR Analysis

Metadata

Advisory analysis (Release Copilot)

Documentation-only bypass (no LLM) — informative only; the merge gate is under System decision below.

Advisory risk level: low

Summary

Documentation-only PR. No application code changes detected.

Risk areas

  • None

Recommended smoke tests

  • None

Recommended regression tests

  • None

Suggested test cases

  1. Validate markdown rendering (low)
    • Open changed markdown files in GitHub preview or rendered output.
    • Verify headings, lists, code blocks, and formatting render correctly.
    • Expected: Documentation renders correctly without formatting issues.
  2. Check links and referenced commands (low)
    • Review changed documentation for internal/external links and command examples.
    • Verify links resolve and commands look current.
    • Expected: Links and referenced commands are valid and up to date.
  3. Confirm docs match operational flow (medium)
    • Compare deployment/rollback steps in documentation with current implementation or scripts.
    • Check that terminology and sequence still match reality.
    • Expected: Documentation is aligned with the current operational process.

System decision (deterministic gate)

Authoritative scores and GO / CONDITIONAL_GO / NO_GO from Dulvarn rules (not raw Copilot risk).

Decision: GO
Risk score: 7.70 / 100
Test integrity score: 96.00 / 100

Reason:
Advisory risk=low maps to risk_score=7.70; test_integrity_score=96.00 from PR structure and suggested coverage. Documentation-only change set; risk is capped. Deterministic gate: GO.

TIRI v0 (heuristic)

Path-based test-gap signals; versioned JSON for tooling and audit.

{
  "coverage_gap_score": 0.0,
  "signals": {
    "docs_only_pr": true,
    "files_total": 1,
    "non_test_code_file_count": 0,
    "sensitive_path_hits": 0,
    "test_file_count": 0
  },
  "version": "0"
}

Generated by Dulvarn • analysis_source=docs_only • provider=system • model=docs_only_bypass
Route: docs_only_bypass

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants