Add Claude Code GitHub Workflow#1
Merged
Merged
Conversation
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
4 tasks
10 tasks
This was referenced Dec 9, 2025
paxcalpt
added a commit
that referenced
this pull request
Feb 5, 2026
Changed from regular space to \enskip command to ensure consistent,
visible spacing after runin subsubsection titles with periods.
Before: {#1. } or {#1.~} - inconsistent spacing
After: {#1.\enskip} - reliable half-em space
Visual verification shows proper spacing in PDF between section title
and following text (e.g., "Manuscripts. A central" with clear space).
Fixes spacing issue reported by Guillaume Jacquemet
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
paxcalpt
added a commit
that referenced
this pull request
Feb 5, 2026
* fix: resolve title spacing and Lithuanian character encoding issues Two bug fixes based on user feedback: 1. **Title spacing**: Removed extra blank line in template.tex between title commands and author list. This fixes unwanted spacing after the document title in generated PDFs. 2. **Character encoding**: Enhanced encode_html_entities() to handle all Unicode characters, not just those with named HTML entities. Characters without named entities now use numeric character references (e.g., č → č, ū → ū, ė → ė). Example: "Vaitkevičiūtė" now correctly converts to "Vaitkevičiūtė" in bioRxiv submission files. Tests: - Added comprehensive tests for Lithuanian characters - All 23 bioRxiv tests pass - All 16 template processor tests pass Fixes reported by Guillaume Jacquemet Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * fix: add newlines after section headers in LaTeX output The real issue reported by Guillaume was that markdown section headers (###) were not creating proper spacing in the LaTeX output. When converted, the section command would run directly into the following text without a blank line. Changes: - Added newline (\n) after all section commands in _convert_headers() - Added newline to the safety net regex that catches unconverted headers - Reverted incorrect template.tex change (that was for document title, not section headers) Before: \subsubsection{Title}Text starts immediately After: \subsubsection{Title}\n\nText properly separated This ensures proper spacing between section titles and content in the generated PDFs. Tests: All 60 md2tex tests pass Fixes issue reported by Guillaume Jacquemet Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * fix: increase spacing after subsubsection titles from 1pt to 8pt The runin subsubsection format was adding a period and space after titles, but only 1pt of spacing afterward was too small, causing text to run together (e.g., "Manuscripts.A" instead of proper spacing). Changed \titlespacing* for \subsubsection from {1pt} to {8pt} to match paragraph spacing and create proper visual separation. Before: "From Static Text to Self-Updating Manuscripts.A central" After: "From Static Text to Self-Updating Manuscripts. A central" Fixes spacing issue reported by Guillaume Jacquemet Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * fix: use \enskip for proper space after subsubsection titles Changed from regular space to \enskip command to ensure consistent, visible spacing after runin subsubsection titles with periods. Before: {#1. } or {#1.~} - inconsistent spacing After: {#1.\enskip} - reliable half-em space Visual verification shows proper spacing in PDF between section title and following text (e.g., "Manuscripts. A central" with clear space). Fixes spacing issue reported by Guillaume Jacquemet Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> * chore: bump version to 1.19.1 - Fixed bioRxiv character encoding for all Unicode characters - Fixed LaTeX section spacing issues in PDF output --------- Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 Installing Claude Code GitHub App
This PR adds a GitHub Actions workflow that enables Claude Code integration in our repository.
What is Claude Code?
Claude Code is an AI coding agent that can help with:
How it works
Once this PR is merged, we'll be able to interact with Claude by mentioning @claude in a pull request or issue comment.
Once the workflow is triggered, Claude will analyze the comment and surrounding context, and execute on the request in a GitHub action.
Important Notes
Security
There's more information in the Claude Code documentation.
After merging this PR, let's try mentioning @claude in a comment on any PR to get started!