All Projects → andstor → jsdoc-action

andstor / jsdoc-action

Licence: Apache-2.0 license
📖 GitHub Action to build JSDoc documentation

Programming Languages

javascript
184084 projects - #8 most used programming language

Projects that are alternatives of or similar to jsdoc-action

Docma
A powerful tool to easily generate beautiful HTML documentation from JavaScript (JSDoc), Markdown and HTML files.
Stars: ✭ 287 (+370.49%)
Mutual labels:  docs, jsdoc
tidy-jsdoc
A clean JSDoc3 template
Stars: ✭ 16 (-73.77%)
Mutual labels:  docs, jsdoc
Parse Comments
Parse JavaScript code comments. Works with block and line comments, and should work with CSS, LESS, SASS, or any language with the same comment formats.
Stars: ✭ 53 (-13.11%)
Mutual labels:  docs, jsdoc
docgen
The docs.json generator for discord.js and its related projects
Stars: ✭ 59 (-3.28%)
Mutual labels:  docs, jsdoc
Assemble
Community
Stars: ✭ 3,995 (+6449.18%)
Mutual labels:  docs, build
Jsdoc Baseline
An experimental, extensible template for JSDoc.
Stars: ✭ 51 (-16.39%)
Mutual labels:  docs, jsdoc
Jsdoc
An API documentation generator for JavaScript.
Stars: ✭ 12,555 (+20481.97%)
Mutual labels:  docs, jsdoc
netlify-build-github-actions
An example of triggering a Netlify build using Github Actions Scheduled Events
Stars: ✭ 31 (-49.18%)
Mutual labels:  github-actions
fdk-aac-win32-builder
libfdk-aac for Windows binary builder
Stars: ✭ 25 (-59.02%)
Mutual labels:  build
deploy-to-vercel-action
🎬▲ Deploy your project to Vercel using GitHub Actions. Supports PR previews and GitHub deployments.
Stars: ✭ 84 (+37.7%)
Mutual labels:  github-actions
jr.mitou.org
未踏ジュニアの公式Webサイトです! YAML ファイルで更新できます 🛠💨
Stars: ✭ 17 (-72.13%)
Mutual labels:  github-actions
action-eslint
🐋🐬 TypeScript/JavaScript ESLint action
Stars: ✭ 24 (-60.66%)
Mutual labels:  github-actions
fnd-docs
Foundation developer docs
Stars: ✭ 33 (-45.9%)
Mutual labels:  docs
django-step-by-step
A Django + Vue reference project that focuses on developer tooling and CI/CD + IaC
Stars: ✭ 86 (+40.98%)
Mutual labels:  github-actions
actions
github actions stuff
Stars: ✭ 39 (-36.07%)
Mutual labels:  github-actions
ghaction-virustotal
GitHub Action to upload and scan files with VirusTotal
Stars: ✭ 105 (+72.13%)
Mutual labels:  github-actions
docs
The documentation for Firefly III
Stars: ✭ 30 (-50.82%)
Mutual labels:  docs
opencloud-docs
AIOT开放平台官方文档。AIOT Open Cloud documents on official website .
Stars: ✭ 68 (+11.48%)
Mutual labels:  docs
ts-scaffold
🏗 ts-scaffold - Scaffold project for Typescript projects, with Unit Tests and basic dependencies set up
Stars: ✭ 13 (-78.69%)
Mutual labels:  github-actions
setup-bats
GitHub Action to setup BATS testing framework
Stars: ✭ 25 (-59.02%)
Mutual labels:  github-actions

jsdoc-action

A GitHub Action to build JSDoc documentation

This is a GitHub Action to build your JavaScript documentation with JSDoc. This action can easily be combined with other deployment actions, in order to publish the generated documentation to for example GitHub Pages. JSDoc templates are also supported.

The following example workflow step will generate documentation for all source files in the ./src directory and output the built files to the ./out directory.

- name: Build
  uses: andstor/jsdoc-action@v1
  with:
    source_dir: ./src
    recurse: true
    output_dir: ./out

Supported platforms

The jsdoc-action is a JavaScript action and is supported on both Linux, MacOS and Windows. The action supports stable versions of Node.js 14 and later.

OS (runs-on) ubuntu-latest macos-latest windows-latest
Support ✅️ ✅️ ✅️

Options ⚙️

The following input variables options can/must be configured:

Input variable Necessity Description Default
source_dir Optional Source directory to build documentation from.
output_dir Optional Output folder for the generated documentation. ./out
recurse Optional Recurse into subdirectories when scanning for source files. false
config_file Optional The path to a JSDoc configuration file.
template Optional The JSDoc template package to install. Will run npm install template.
template_dir Optional The relative location of the template files directory within the template package.
front_page Optional The path to a Markdown file to be used as a the front page. Normally README.md.

Templates 💅

You can use JSDoc templates with this action.
Just set the template input variable to the name of the template you want to use. This needs to be template's package name.

If the template's template files is located somewhere else than the package's root, you need to specify this. Set the template_dir input variable to the location of the template folder (contains a publish.js file).

For example, to use the JSDoc DocStrap template, set the template input variable to ink-docstrap and the template_dir to the string template.

JSDoc Configuration file 📄

To use a JSDoc configuration file located in your repository, you will need to specify the path to the file in the config_file input variable. Normally, if you use the actions/checkout, this will just resolve to conf.json or conf.js.

Examples

GitHub Pages 🚀

An example for deploying JSDoc generated documentation to GitHub Pages with actions-gh-pages.

This jsdoc-action workflow configuration uses the Minami JSDoc template and uses the root README.md file as the front page.

name: GitHub pages

on:
  push:
    branches:
      - master

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v2

      - name: Build
        uses: andstor/jsdoc-action@v1
        with:
          source_dir: ./src
          output_dir: ./out
          config_file: conf.json
          template: minami
          front_page: README.md

      - name: Deploy
        uses: peaceiris/actions-gh-pages@v3
        with:
          deploy_key: ${{ secrets.ACTIONS_DEPLOY_KEY }}
          publish_dir: ./out

License

Copyright © 2020 André Storhaug

The jsdoc-action GitHub action is licensed under the Apache License, Version 2.0.
See the LICENSE file for more information.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].