Code blocks in READMEs on entire.io render with an extra empty line at the end
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 67/100
Research direction
Start by tracing how README Markdown is rendered on the repo overview page and how fenced code block text is split into displayed lines; the issue identifies a trailing newline as a likely cause. Compare the rendered block with the source README, then check the related issue #2745 for context. Done when code blocks no longer show an extra empty final line across the listed page types.
Written by the indexing model from the issue text.
Description
What happened?
Every fenced code block in a README on the repo overview page shows one more line than the source has. The last line is empty.
For example, this 3-line block renders as 4 lines:
git clone https://github.com/AlexVCS/nba-scores.git
cd nba-scores
pnpm i
Steps to reproduce
- Open https://entire.io/gh/AlexVCS/nba-scores#:~:text=git%20clone%20https%3A//github.com/AlexVCS/nba%2Dscores.git (jumps to the "Clone the repo" code block in the README)
- Compare the code blocks with https://github.com/AlexVCS/nba-scores#readme
Entire CLI version
N/A (entire.io web UI)
OS and architecture
macOS, Chromium-based browser
Agent
N/A (entire.io web UI)
Terminal
No response
Logs / debug output
Additional context
Likely cause: the code block's text ends with a trailing newline, and the code viewer splits on newlines, which yields an empty final line. Stripping one trailing newline before rendering should fix it.
Related: other markdown issue
Not specific to my repo: every README code block also has the extra line on https://entire.io/gh/entireio/entire-brain (mirrored) and https://entire.io/et/hackathone/hackathon (Entire-native).
- Dominant language
- Go
- Stars
- 5.1k
- Forks
- 475
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 205
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from entireio/cli
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
entireio/cli#2416 · 1 comment ·
Maintainers usually reply within 1 day
-
Stale `entire configure --agent` hints in investigate and review error messagesPossibly taken @suhaanthayyil claimed this 57 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Codex last_assistant_message is parsed then discarded on Stop/SubagentStopPossibly taken @Vishal202-rgb claimed this 48 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
entireio/cli#2064 · 1 comment ·
Maintainers usually reply within 1 day
-
Codex input_image base64 silently destroyed by JSONL redactionPossibly taken @suhaanthayyil claimed this 75 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
hyperledger/fabric-x-orderer#1409 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
needs-area
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Azure/typespec-azure#5936 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
-
Fix mode unpins a reusable workflow call when the same repository is also used as a step actionOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github/gh-actions-lock#261 ·
Maintainers usually reply within 1 day