-
Notifications
You must be signed in to change notification settings - Fork 0
Comparing changes
Open a pull request
base repository: 1mb-dev/markgo
base: v2.3.0
head repository: 1mb-dev/markgo
compare: v2.3.1
- 9 commits
- 30 files changed
- 1 contributor
Commits on Feb 4, 2026
-
fix(lint): resolve 62 mechanical lint issues across 17 files
Fix httpNoBody (19x), importShadow (19x), hugeParam (9x), paramTypeCombine (2x), emptyStringTest (1x), and misspell (1x) issues flagged by golangci-lint. These are safe, no-behavior-change fixes that unblock tag-triggered CI where only-new-issues has no base ref.
Configuration menu - View commit details
-
Copy full SHA for 70c10c7 - Browse repository at this point
Copy the full SHA 70c10c7View commit details -
fix(lint): resolve structural lint issues across commands and handlers
- Remove unnecessary bare braces in route group blocks (serve, seo) - Extract setupServer and configureGinMode to reduce cyclomatic complexity - Add bounds check before slice access in formatBytes (gosec G602) - Rename ExportConfig to Config to avoid package stutter (revive) - Handle errcheck: fs.Parse, user.Current, os.Stdin.Stat return values - Add nolint for safe type assertions with zero-value fallback in base.go
Configuration menu - View commit details
-
Copy full SHA for 7028ce8 - Browse repository at this point
Copy the full SHA 7028ce8View commit details -
fix(lint): add nolint directives for HTML attribute quoting false pos…
…itives The sprintfQuotedString lint rule flags fmt.Sprintf calls that use "%s" inside quoted strings, suggesting %q instead. These are HTML attribute values (e.g., content="%s") where quotes are HTML syntax, not Go string quoting. Using %q would produce double-escaped output.
Configuration menu - View commit details
-
Copy full SHA for 4d3add5 - Browse repository at this point
Copy the full SHA 4d3add5View commit details -
fix(web): remove navbar tagline fallback to long description
- Remove Description fallback in brand-subtitle; render nothing if no tagline is set instead of cramming the full blog description into the navbar - Add BLOG_TAGLINE to demo deploy workflow
Configuration menu - View commit details
-
Copy full SHA for 76a41c0 - Browse repository at this point
Copy the full SHA 76a41c0View commit details -
fix(css): add breathing space between page-header and body content
Add margin-bottom to .page-header at all breakpoints so the hero section on tags, contact, and about pages doesn't crowd the main body content. Also bump mobile bottom padding from spacing-6 to spacing-8 for consistency.
Configuration menu - View commit details
-
Copy full SHA for 0a84280 - Browse repository at this point
Copy the full SHA 0a84280View commit details -
fix(export): improve static export fidelity and fix engine issues
- Export 404.html for GitHub Pages custom error page support - Pass BuildInfo to export handlers so footer shows version instead of "unknown" - Fix contact page title to include blog title suffix (consistent with other pages) - Replace placeholder GitHub links in templates with actual project URL
Configuration menu - View commit details
-
Copy full SHA for 522d21a - Browse repository at this point
Copy the full SHA 522d21aView commit details -
fix(web): standardize page-header to full-width layout across all pages
Move page-header outside container wrapper on categories, tags, contact, and about pages to match the full-width pattern used by articles, tag, category, and 404 pages. This ensures the gradient background spans edge-to-edge consistently while content remains container-constrained.
Configuration menu - View commit details
-
Copy full SHA for b6b6e41 - Browse repository at this point
Copy the full SHA b6b6e41View commit details -
Configuration menu - View commit details
-
Copy full SHA for 82046fa - Browse repository at this point
Copy the full SHA 82046faView commit details -
Configuration menu - View commit details
-
Copy full SHA for 04a066a - Browse repository at this point
Copy the full SHA 04a066aView commit details
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 v2.3.0...v2.3.1