Skip to content

fix: strip leading UTF-8 BOM from aggregated GitHub content #43

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vbreuss merged 1 commit into from
Jun 4, 2026
Merged

fix: strip leading UTF-8 BOM from aggregated GitHub content #43

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion Pipeline/Build.Pages.cs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -339,6 +339,11 @@ static string EnsureSidebarPosition(string content, int position)
static string Base64Decode(string base64EncodedData)
{
byte[] base64EncodedBytes = Convert.FromBase64String(base64EncodedData);
return Encoding.UTF8.GetString(base64EncodedBytes);
// The GitHub API returns file bytes verbatim, so a UTF-8 BOM survives into the
// decoded string. A leading BOM (U+FEFF) before the first markdown heading stops
// Docusaurus from parsing it (the heading renders as a literal paragraph) and also
// breaks StripReadmeFront's H1 detection, since char.IsWhiteSpace('') is false
// and TrimStart() leaves it in place. Drop it once at the single decode chokepoint.
return Encoding.UTF8.GetString(base64EncodedBytes).TrimStart('');
}
}
Loading