Skip to content

Align README with current command scope#1

Open
kriptoburak wants to merge 20 commits into
warlockoussama:mainfrom
kriptoburak:codex/update-readme-command-scope
Open

Align README with current command scope#1
kriptoburak wants to merge 20 commits into
warlockoussama:mainfrom
kriptoburak:codex/update-readme-command-scope

Conversation

@kriptoburak

Copy link
Copy Markdown

Summary

  • Update the README title, overview, and feature list to match the current CLI surface.
  • Replace the stale "view-only" posting answer with the documented write commands.
  • Add credential safety guidance for browser cookies, auth_token, ct0, and local files, plus a short companion-tools note for jobs outside this CLI scope.

Validation

  • npx --yes markdown-link-check README.md --quiet
  • git diff --check
  • uv run ruff check .
  • uv run mypy twitter_cli
  • uv run --extra dev pytest -q

@kriptoburak kriptoburak force-pushed the codex/update-readme-command-scope branch from 299de6a to 75f3b5a Compare June 13, 2026 08:09
@warlockoussama warlockoussama force-pushed the main branch 17 times, most recently from fc0806c to e5c2919 Compare June 15, 2026 16:10
@kriptoburak

Copy link
Copy Markdown
Author

Merged current upstream main and resolved the README conflict in d6da100. The conflicting final download link was identical on both sides, so the branch keeps one canonical link and preserves the existing Xquik/TweetClaw companion note. Validation passed: git diff whitespace check, conflict-marker scan, README markdown-link-check, and changed-diff public-hygiene scan.

@warlockoussama warlockoussama force-pushed the main branch 5 times, most recently from fc763ef to c403375 Compare June 16, 2026 07:50
@kriptoburak

Copy link
Copy Markdown
Author

Merged current upstream main and resolved the README conflict without changing the command-scope clarification.

Validation passed:

  • conflict-marker scan
  • git diff --check
  • changed-line public-hygiene and dash scan against the PR diff
  • npx --yes markdown-link-check README.md --quiet
  • direct TweetClaw URL check

@kriptoburak

Copy link
Copy Markdown
Author

Resolved the current README merge conflict and pushed the repaired branch.

Validation passed:

  • git diff --check
  • exact conflict-marker scan on README.md
  • npx --yes markdown-link-check README.md --quiet
  • staged diff public-hygiene scan

@warlockoussama warlockoussama force-pushed the main branch 2 times, most recently from a2bb17f to 8332ebf Compare June 21, 2026 10:31
@kriptoburak

Copy link
Copy Markdown
Author

Merged current upstream main after the force-update and resolved the README conflict in f42cabf.

Resolution:

  • Preserves the command-scope clarification for read and write commands.
  • Preserves the TweetClaw companion note for repeatable API, MCP, OpenClaw, monitor, webhook, DM, media, and giveaway workflows.
  • Keeps the upstream download links unchanged.

Validation:

  • conflict-marker scan
  • git diff --check
  • npx --yes markdown-link-check README.md --quiet
  • changed README secret-pattern scan

@kriptoburak

Copy link
Copy Markdown
Author

Merged current upstream main and resolved the duplicate README download-link conflict in 2159b8a. The repair removes conflict markers around identical final-link text and preserves the command-scope clarification plus TweetClaw companion note. Validation passed: conflict-marker scan, git diff check, README markdown-link-check, and changed-diff public-hygiene scan.

@kriptoburak

Copy link
Copy Markdown
Author

Merged current upstream main and resolved the duplicate README download-link conflict in 93709b0. The conflicting final link was identical on both sides, so the repair only removes conflict markers and keeps the command-scope clarification plus TweetClaw companion note unchanged.

Validation passed:

  • conflict-marker scan
  • git diff check
  • README markdown-link-check
  • changed-diff public-hygiene scan

@kriptoburak

Copy link
Copy Markdown
Author

Merged current upstream main and resolved the duplicate README download-link conflict in 90ce977. The repair keeps one canonical download link and preserves the command-scope clarification plus TweetClaw companion note.

Validation passed:

  • conflict-marker scan
  • git diff check
  • README markdown-link-check
  • changed-diff public-hygiene scan

@kriptoburak

Copy link
Copy Markdown
Author

Merged current upstream main again and resolved the duplicate README download-link conflict in 8f3583e. The repair keeps one canonical download link and preserves the command-scope clarification plus TweetClaw companion note.

Validation passed:

  • git diff --check
  • conflict-marker scan
  • README markdown-link-check
  • changed-diff public-hygiene scan

@kriptoburak

Copy link
Copy Markdown
Author

Merged current upstream main and resolved the duplicate README download-link conflict in e820dfa. The repair keeps one canonical download link and preserves the command-scope clarification plus TweetClaw companion note.

Validation passed:

  • git diff --check
  • conflict-marker scan
  • npx --yes markdown-link-check README.md --quiet
  • fork-parent readback

@kriptoburak

Copy link
Copy Markdown
Author

Merged current upstream main in d35fde8 to clear the README conflict. Validation passed: git diff --check; markdown-link-check README.md.

@kriptoburak

Copy link
Copy Markdown
Author

Resolved the README merge conflict and revalidated links with npx --yes markdown-link-check README.md --quiet. The branch is updated.

@kriptoburak

Copy link
Copy Markdown
Author

Merged current upstream main and resolved the README conflict in 95ad08c. The repair keeps the command-scope clarification, TweetClaw companion note, and upstream download link once. Validation passed: git diff --check, conflict-marker scan, and npx --yes markdown-link-check README.md --quiet.

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