Skip to content

Latest commit

 

History

History
81 lines (69 loc) · 11.9 KB

README.md

File metadata and controls

81 lines (69 loc) · 11.9 KB

workflows-to-markdown NPM version

Workflows to markdown is supposed to generate a map of your event-workflows. It will show you what event causes which workflows to run.

CLI

Usage: cli [options]

Options:
  -o, --output <path>  path to an .md file that you want your documentation to be saved there. (default:
                       ".github/workflows/README.md")
  -i, --input <path>   path to a directory that contains your workflow files. (default: ".github/workflows")
  -h, --help           display help for command

Install

Note: You can use Workflows to Markdown Action if you want to automate the process of map generation.

Install with npm:

$ npm install --save-dev workflows-to-markdown

Usage

After installation you can run workflows2md on your terminal in your project's path. you can change the input and output location using CLI options;

workflows2md -i /.github/workflows -o WORKFLOWS.md

Output Example

This is a map that has been generated from AsyncAPI's website workflows.

Event-Workflow Map

pull_ request_ target opened edited, synchronizereopened, ready_for_reviewunlocked, unlabeled, labeled
issues opened reopened unlabeled, labeled, closed, deleted edited
push master any **-release, next
pull_ request opened ready_for_review, synchronize, reopened edited
issue_ comment created edited
pull_ request_ review submitted edited
schedule At 12:00 AM
release published
discussion created
pull_ request_ review_ commentedited, created

Workflows

Workflow Description
Automerge For Humans Your first comment after name parameter in workflow will appear here.
Automerge release bump PR Your first comment after name parameter in workflow will appear here.
Notify slack Your first comment after name parameter in workflow will appear here.
Lint PR title Your first comment after name parameter in workflow will appear here.
Welcome first time contributors Your first comment after name parameter in workflow will appear here.
Remove ready-to-merge label Your first comment after name parameter in workflow will appear here.
Deploy to Netlify Your first comment after name parameter in workflow will appear here.
Sentiment Analysis Your first comment after name parameter in workflow will appear here.
Bump package version in dependent repos - if Node project Your first comment after name parameter in workflow will appear here.
Release - if Node project Your first comment after name parameter in workflow will appear here.
autoupdate Your first comment after name parameter in workflow will appear here.
PR testing - if Go project Your first comment after name parameter in workflow will appear here.
PR testing - if Node project Your first comment after name parameter in workflow will appear here.
Add ready-to-merge or do-not-merge label Your first comment after name parameter in workflow will appear here.
Create help comment Your first comment after name parameter in workflow will appear here.
Notify on failing automerge Your first comment after name parameter in workflow will appear here.
Manage stale issues and PRs Your first comment after name parameter in workflow will appear here.
Version bump - if Node.js project There is no need to substract "v" from the tag as version script handles it
Announce releases in different channels Your first comment after name parameter in workflow will appear here.