pip install markitdown-ocr

[flynnjustin24]

pip install markitdown-ocr

Originally posted by @flynnjustin24 in https://github.com/gh-codespace-create/demo-repository/pull/2#issuecomment-5187407573

[flynnjustin24]

• Visual Studio Code Server
• By using the software, you agree to
• the Visual Studio Code Server License Terms (https://aka.ms/vscode-server-license) and
• the Microsoft Privacy Statement (https://privacy.microsoft.com/en-US/privacystatement).

[flynnjustin24]

https://prod.liveshare.vsengsaas.visualstudio.com/join?3FF9790B65F13F544853A6CEC269307791DD

[flynnjustin24]

.github/workflows/smoke-cursor.lock.yml

[flynnjustin24]

evals/codesimplifier

[flynnjustin24]

gh-aw-metadata: {"schema_version":"v3","frontmatter_hash":"...","strict":true,"agent_id":"copilot"}

___ ...ASCII logo...

This file was automatically generated by gh-aw. DO NOT EDIT.

...

Secrets used:

- COPILOT_GITHUB_TOKEN

- GITHUB_TOKEN

Custom actions used:

- actions/checkout@de0fac2e... # v6.0.2

- actions/upload-artifact@bbbca2... # v4

[flynnjustin24]

github/workflows/deploy.yml

[flynnjustin24]

github/workflows/ci.yml

[flynnjustin24]

pip install markitdown-ocr

[flynnjustin24]

github/steps/1-step.md

[flynnjustin24]

github/steps/x-review.md

[flynnjustin24]

[flynnjustin24]

GitHub takes the security of our software products and services seriously, including the open source code repositories managed through our GitHub organizations, such as cli.

If you believe you have found a security vulnerability in GitHub CLI, you can report it to us in one of two ways:

• Report it to this repository directly using private vulnerability reporting.

  • Include a description of your investigation of the GitHub CLI's codebase and why you believe an exploit is possible.
  • POCs and links to code are greatly encouraged.
  • Such reports are not eligible for a bounty reward.

• Submit the report through HackerOne to be eligible for a bounty reward.

Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.

A dependency having a CVE does not mean gh has a vulnerability. We use govulncheck to determine whether vulnerable symbols are actually reachable from gh's code. If you are reporting a dependency CVE, please include evidence that the issue is exploitable in gh: a call chain into the affected symbols or a proof of concept. Reports that only list a dependency version and CVE without demonstrating impact will be closed.

Thanks for helping make GitHub safe for everyone.

[flynnjustin24]

$ gh repo clone cli/cli

[flynnjustin24]

GitHub Agentic Workflows Factory Tour

Important

GitHub Agentic Workflows and the gh-aw CLI are in public preview. You may notice product changes, rough edges, or minor differences from the screenshots and examples in this workshop.

• Workshop docs

What you will learn to build

Build a real AI-powered GitHub workflow from scratch and leave with a safe production-style agentic automation you can adapt to your own repositories.

Why this workshop

Most workflow tutorials stop at toy examples. This workshop takes you all the way to a useful end result: an agentic workflow that runs in GitHub Actions, inspects a repository, and publishes a daily status report automatically.

By the time you finish, you will know how to:

• define an agentic workflow in Markdown
• use the gh-aw CLI to validate, run, and iterate on workflows
• connect triggers, prompts, and GitHub context into one practical automation
• adapt the pattern for scheduled reporting, documentation upkeep, PR review, and more

What you'll build

You'll build a scheduled, AI-powered repository status report that runs in GitHub Actions and posts a useful summary without custom shell-script orchestration.

Who this is for

You are...	You'll get...
A developer new to agentic workflows	A clear, end-to-end path from zero to a working automation
A GitHub Actions user	A practical mental model for when agentic workflows are a better fit than classic YAML and scripts
A platform or DevOps engineer	A reusable pattern for AI-assisted repository triage with auditable runs in GitHub
An evaluator, mentor, or workshop host	A hands-on artifact that makes agentic workflow concepts easy to demonstrate and assess

What makes this different from a classic Actions tutorial

Instead of spending most of your time wiring together scripts, conditionals, and API calls, you define the workflow in a Markdown brief and let the agent reason over the repository at runtime.

That means you focus on:

• the task you want completed
• the repository context the agent should use
• the trigger that should run the workflow
• the output that should be published back to GitHub

Ready to begin?

➡️ Start with workshop/00-welcome.md

Note

Microsoft and GitHub facilitators: Request a demo environment at aka.ms/golden-ticket.

---

©️ GitHub • Code of Conduct • MIT License

[flynnjustin24]

packages/markitdown-ocr/README.md