Skip to content

[docs] Fix Telegram README Markdownlint#345

Merged
justfinethanku merged 2 commits into
NateBJones-Projects:mainfrom
alanshurafa:codex/telegram-markdownlint-fix
Jun 8, 2026
Merged

[docs] Fix Telegram README Markdownlint#345
justfinethanku merged 2 commits into
NateBJones-Projects:mainfrom
alanshurafa:codex/telegram-markdownlint-fix

Conversation

@alanshurafa

Copy link
Copy Markdown
Collaborator

Summary

  • Add required blank lines around fenced code blocks in integrations/telegram-capture/README.md
  • Keep this PR intentionally tiny so full-repo Markdownlint can be unblocked before recipe PRs open

Verification

  • npx --yes markdownlint-cli2 --config .github/.markdownlint.jsonc "**/*.md" "#node_modules"
  • git diff --check

@github-actions github-actions Bot added the integration Contribution: MCP extension or capture source label Jun 6, 2026
@alanshurafa

Copy link
Copy Markdown
Collaborator Author

This PR is the minimal repo-wide Markdownlint unblocker for the ingestion PR stack. Local and GitHub Markdownlint are green; the remaining blocker is required review. Once this lands, the prepared ingestion branches can be opened against main without known-red lint checks.

@justfinethanku justfinethanku left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maintainer review: clean Markdownlint-only README spacing fix. Checks are green, and this preserves the existing Telegram integration content while unblocking the ingestion PR stack.

@justfinethanku justfinethanku merged commit 4ba44a3 into NateBJones-Projects:main Jun 8, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

integration Contribution: MCP extension or capture source

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants