Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: taskade/docs
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: taskade/docs
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: docs/live-render-fixes
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 1 commit
  • 2 files changed
  • 1 contributor

Commits on Jun 5, 2026

  1. docs: fix live render leakage — recipes fence trap + getting-started … 

    …newlines

Found by the post-merge multi-agent live render audit of docs.taskade.com:

- automation/recipes.md: a stray bare code fence trapped the entire 'Recipe 2:
  Automated Social Media Posting' section (heading + hint + prose) inside a code
  block, and two 4-backtick fences mismatched their 3-backtick openers. Removed
  the stray fence and normalized the closers so Recipe 2 renders as a heading +
  success-hint callout, and the project-structure / JSON examples render as
  proper code blocks.
- genesis/getting-started.md: literal backslash-n sequences leaked into visible
  prose (lines 9, 11, 61) and collapsed a 'what to do next' bullet list (line
  390). Converted to real paragraph breaks and bullet lines.

(workspaces/markdown.md retains \n inside code-span syntax examples — that is an
intentional way to show multi-line snippets within a single table cell.)

Verified: fences balanced, Recipe 2 + hint render in prose, 0 literal \n in
getting-started prose.
    @johnxie
    johnxie committed Jun 5, 2026
    Configuration menu
    Copy the full SHA
    1a2c55c View commit details
    Browse the repository at this point in the history
Loading