Permalink
Checking mergeability…
Don’t worry, you can still create the pull request.
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 7 commits
- 8 files changed
- 3 contributors
Commits on Jul 22, 2026
-
build: update cross-repo angular dependencies
See associated pull request for more information.
-
docs: fix first heading rendering as paragraph on two template guides
The ng-container and binding template guide files each began with a UTF-8 BOM (EF BB BF) before the leading `#`. The docs markdown parser only promotes `#` to an H1 when it is the first character on the line, so the BOM demoted the title to paragraph text (`<p># ...</p>`) and the standard docs header (breadcrumbs, page title, edit button) never rendered. Stripping the BOM restores `#` as the first character, so both pages now generate the proper `<header class="docs-header">` block. Verified by rebuilding //adev/src/content/guide/templates:templates and inspecting the generated HTML. Fixes #69889
-
fix(docs-infra): fail the guide build when a markdown file starts wit…
…h a BOM A leading UTF-8 byte order mark (U+FEFF) before the first `#` stops the Markdown parser from recognizing the heading, so the guide renders its title as a paragraph and drops the standard docs header. The character is invisible, so it cannot be caught in review. Add a check in the guides generation pipeline that throws when a source file starts with a BOM, failing the build with the offending file name. This sits alongside the existing unknown-anchor check and prevents the regression fixed in #69889 from recurring.
-
Update pnpm lock after it got desychronized in 791b064 build: update all non-major dependencies
-
-
-
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff g3...main