Skip to content

fix: invalid // comment headers in YAML/Justfile#47

Merged
hyperpolymath merged 1 commit into
mainfrom
claude/practical-newton-9eFe2
Jun 14, 2026
Merged

fix: invalid // comment headers in YAML/Justfile#47
hyperpolymath merged 1 commit into
mainfrom
claude/practical-newton-9eFe2

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Problem

An estate-standardization script wrote the Owner: header line using C-style // comment syntax into files that use # comments. // is not a valid comment in YAML or in just, so it breaks those parsers.

Affected files (line 2 each):

  • .gitlab-ci.yml — YAML uses #
  • Justfilejust uses #

Fix

Changed the leading // Owner: to # Owner: in those two files only:

 # SPDX-License-Identifier: MPL-2.0
-// Owner: Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>
+# Owner: Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>

Left intentionally unchanged

Files where // is a valid comment were not touched:

  • compiler/tangle-lsp/src/backend.rs (Rust — //)
  • contractiles/README.adoc and other .adoc (AsciiDoc — //)
  • .md files

(.github/workflows/lean-proofs.yml already used # Owner: correctly and was not modified.)

https://claude.ai/code/session_017TXizM5c1Yd9HWf7Y15YH2


Generated by Claude Code

The estate-standardization "Owner:" header was written with C-style // in
files that use # comments (.gitlab-ci.yml, Justfile), which is invalid and
breaks those parsers. Changed `// Owner:` -> `# Owner:`. (.adoc/.rs files are
left as-is: // is a valid comment there.)

https://claude.ai/code/session_017TXizM5c1Yd9HWf7Y15YH2
@hyperpolymath hyperpolymath marked this pull request as ready for review June 14, 2026 10:51
@hyperpolymath hyperpolymath merged commit 7cd0f79 into main Jun 14, 2026
11 of 12 checks passed
@hyperpolymath hyperpolymath deleted the claude/practical-newton-9eFe2 branch June 14, 2026 10:51
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.

2 participants