✨ A GitHub Action that automatically generates & updates markdown content (like your README.md) from external or remote files.
195
stars
747
commits
JavaScript
primary language
Jan 31, 2026
updated
A GitHub Action that automatically generates & updates markdown content (like your README.md) from external or remote files.
Ask questions in the GitHub issues
To make your repo more appealing and useful you need to provide example code snippets in your README.md. Manually copy and pasting each code snippet in their respective places in your README would be inefficient and time-consuming.
This problem can be solved using markdown-autodocs a GitHub Action that automatically generates & updates markdown content (like your README.md) from external or remote files. You need to add markers in your README.md that will tell markdown-autodocs where to insert the code snippet.
Get code from an external file or URL and insert it in your markdown.
Options:
src: The relative path to the code to pull in, or the URL where the raw code liveslines (optional): a range with lines of code which will then be replaced with code from the file. The line range should be defined as: "lines=startLine-EndLine" (for example: "lines=22-44"). Please see the example belowsyntax (optional): Syntax will be inferred by fileType if not specifiedheader (optional): Will add header comment to code snippet. Useful for pointing to relative source directory or adding live doc linksOptions are concatenated via the & sign.
For example (CODE:src=readme.md&lines=10-20)
Get JSON contents from an external file and convert it into an HTML table and insert's it in your markdown.
Options:
src: The relative path to the JSON file to pull in.
Get the list of the latest artifacts generated from a workflow run. Generates a workflow artifacts table consists of artifacts download and workflow URL in an HTML table and inserts it in your markdown file.
Install markdown-autodocs CLI:
npm i -g markdown-autodocs
markdown-autodocs CLI usage:
dineshsonachalam@macbook ~ % markdown-autodocs --help
Usage: markdown-autodocs [options]
Options:
-o, --outputFilePath <outputFilePaths...> Output file paths
-c, --category <categories...> code-block, json-to-html-table, workflow-artifact-table
-r, --repo <type> Repo name
-b, --branch <type> Branch name
-a, --accessToken <type> Github Access token
-h, --help display help for command
markdown-autodocs -c code-block -o ./README.md
markdown-autodocs -c json-to-html-table -o ./README.md
markdown-autodocs -c workflow-artifact-table -o ./README.md -r $REPO -b $BRANCH -a $ACCESSTOKEN
Add the following step at the end of your job, after other steps that might add or change files.
uses: dineshsonachalam/markdown-autodocs@v1.0.7
- name: Markdown autodocs
- uses: dineshsonachalam/markdown-autodocs@v1.0.7
with:
# Optional, defaults to author of the commit that triggered the run
commit_author: Author <actions@github.com>
# Optional, defaults to "actions@github.com"
commit_user_email: actions@github.com
# Optional, but recommended
# Defaults to "Apply automatic changes"
commit_message: Apply automatic changes
# Optional branch name where commit should be pushed to.
# Defaults to the current branch.
branch: feature-123
# Optional output file paths, defaults to '[./README.md]'.
output_file_paths: '[./README.md]'
# Categories to automatically sync or transform its contents in the markdown files.
# Defaults to '[code-block,json-to-html-table,workflow-artifact-table]'
categories: '[code-block,json-to-html-table,workflow-artifact-table]'
| Artifact | Workflow |
|---|---|
| module-dependencies-license-report | tests |
| size-of-dependencies | tests |
| vulnerabilities-audit-report | tests |
| Repo | Stars | Usage |
|---|---|---|
| Iro.js | 🎨 Modular, design-conscious color picker widget for JavaScript - with support for a bunch of color formats | |
| Fireworks.js | 🎆 A simple fireworks library! Ready to use components available for React, Vue 3, Svelte, Angular, Preact, Solid, and Web Components | |
| BPMN engine | A BPMN engine, meant to be embedded in Go applications with minimal hurdles, and a pleasant developer experience using it. This approach can increase transparency for non-developers | |
| FOSS Community Acronyms | List of abbreviations used within the FOSS community, and their definitions and usages | |
| TWallpaper | 🌈 Multicolor gradient wallpaper created algorithmically and shimmers smoothly | |
| Dusk UI Kit | 🧱 Dusk UI component library | |
| LTSM Stock Predictor | Predicting different stock prices using Long Short-Term Memory Recurrent Neural Network in Python using TensorFlow 2 and Keras | |
| PowerShell | PowerShell Core Profile Directory | |
| Mincecraft Observability extension | Uses minecraft as a client for viewing observability metrics | |
| eKonomic Research Python Toolkit | A NLP Library for Social Science Research | |
| The argument parser for bio-c++ tools | The Sharg parser offers a neat and easy-to-use header-only library for argument parsing in C++ |
JavaScript
71.9%
Python
27.5%
✨ A GitHub Action that automatically generates & updates markdown content (like your README.md) from external or remote files.
195
stars
747
commits
JavaScript
primary language
Jan 31, 2026
updated
A GitHub Action that automatically generates & updates markdown content (like your README.md) from external or remote files.
Ask questions in the GitHub issues
To make your repo more appealing and useful you need to provide example code snippets in your README.md. Manually copy and pasting each code snippet in their respective places in your README would be inefficient and time-consuming.
This problem can be solved using markdown-autodocs a GitHub Action that automatically generates & updates markdown content (like your README.md) from external or remote files. You need to add markers in your README.md that will tell markdown-autodocs where to insert the code snippet.
Get code from an external file or URL and insert it in your markdown.
Options:
src: The relative path to the code to pull in, or the URL where the raw code liveslines (optional): a range with lines of code which will then be replaced with code from the file. The line range should be defined as: "lines=startLine-EndLine" (for example: "lines=22-44"). Please see the example belowsyntax (optional): Syntax will be inferred by fileType if not specifiedheader (optional): Will add header comment to code snippet. Useful for pointing to relative source directory or adding live doc linksOptions are concatenated via the & sign.
For example (CODE:src=readme.md&lines=10-20)
Get JSON contents from an external file and convert it into an HTML table and insert's it in your markdown.
Options:
src: The relative path to the JSON file to pull in.
Get the list of the latest artifacts generated from a workflow run. Generates a workflow artifacts table consists of artifacts download and workflow URL in an HTML table and inserts it in your markdown file.
Install markdown-autodocs CLI:
npm i -g markdown-autodocs
markdown-autodocs CLI usage:
dineshsonachalam@macbook ~ % markdown-autodocs --help
Usage: markdown-autodocs [options]
Options:
-o, --outputFilePath <outputFilePaths...> Output file paths
-c, --category <categories...> code-block, json-to-html-table, workflow-artifact-table
-r, --repo <type> Repo name
-b, --branch <type> Branch name
-a, --accessToken <type> Github Access token
-h, --help display help for command
markdown-autodocs -c code-block -o ./README.md
markdown-autodocs -c json-to-html-table -o ./README.md
markdown-autodocs -c workflow-artifact-table -o ./README.md -r $REPO -b $BRANCH -a $ACCESSTOKEN
Add the following step at the end of your job, after other steps that might add or change files.
uses: dineshsonachalam/markdown-autodocs@v1.0.7
- name: Markdown autodocs
- uses: dineshsonachalam/markdown-autodocs@v1.0.7
with:
# Optional, defaults to author of the commit that triggered the run
commit_author: Author <actions@github.com>
# Optional, defaults to "actions@github.com"
commit_user_email: actions@github.com
# Optional, but recommended
# Defaults to "Apply automatic changes"
commit_message: Apply automatic changes
# Optional branch name where commit should be pushed to.
# Defaults to the current branch.
branch: feature-123
# Optional output file paths, defaults to '[./README.md]'.
output_file_paths: '[./README.md]'
# Categories to automatically sync or transform its contents in the markdown files.
# Defaults to '[code-block,json-to-html-table,workflow-artifact-table]'
categories: '[code-block,json-to-html-table,workflow-artifact-table]'
| Artifact | Workflow |
|---|---|
| module-dependencies-license-report | tests |
| size-of-dependencies | tests |
| vulnerabilities-audit-report | tests |
| Repo | Stars | Usage |
|---|---|---|
| Iro.js | 🎨 Modular, design-conscious color picker widget for JavaScript - with support for a bunch of color formats | |
| Fireworks.js | 🎆 A simple fireworks library! Ready to use components available for React, Vue 3, Svelte, Angular, Preact, Solid, and Web Components | |
| BPMN engine | A BPMN engine, meant to be embedded in Go applications with minimal hurdles, and a pleasant developer experience using it. This approach can increase transparency for non-developers | |
| FOSS Community Acronyms | List of abbreviations used within the FOSS community, and their definitions and usages | |
| TWallpaper | 🌈 Multicolor gradient wallpaper created algorithmically and shimmers smoothly | |
| Dusk UI Kit | 🧱 Dusk UI component library | |
| LTSM Stock Predictor | Predicting different stock prices using Long Short-Term Memory Recurrent Neural Network in Python using TensorFlow 2 and Keras | |
| PowerShell | PowerShell Core Profile Directory | |
| Mincecraft Observability extension | Uses minecraft as a client for viewing observability metrics | |
| eKonomic Research Python Toolkit | A NLP Library for Social Science Research | |
| The argument parser for bio-c++ tools | The Sharg parser offers a neat and easy-to-use header-only library for argument parsing in C++ |
JavaScript
71.9%
Python
27.5%