All Projects → SwiftDocOrg → github-wiki-publish-action

SwiftDocOrg / github-wiki-publish-action

Licence: MIT license
GitHub Action that publishes the contents of a directory to your project's wiki

Programming Languages

shell
77523 projects
Dockerfile
14818 projects

Projects that are alternatives of or similar to github-wiki-publish-action

CodeforcesApiPy
Implementation of https://codeforces.com API
Stars: ✭ 17 (-77.33%)
Mutual labels:  github-wiki, github-actions
Seleniumbase
A Python framework that inspires developers to become better test automation engineers. 🧠💡
Stars: ✭ 2,520 (+3260%)
Mutual labels:  github-actions
upx-action
Strips and runs upx on binaries
Stars: ✭ 17 (-77.33%)
Mutual labels:  github-actions
Goreleaser
Deliver Go binaries as fast and easily as possible
Stars: ✭ 9,290 (+12286.67%)
Mutual labels:  github-actions
gh-pages-action
A GitHub Action to deploy a static site on GitHub Pages.
Stars: ✭ 26 (-65.33%)
Mutual labels:  github-actions
Setup Php
GitHub action to set up PHP with extensions, php.ini configuration, coverage drivers, and various tools.
Stars: ✭ 1,945 (+2493.33%)
Mutual labels:  github-actions
github-run-tests-action
mabl Github Actions implementation
Stars: ✭ 39 (-48%)
Mutual labels:  github-actions
GLaDOS-CheckIn
GLaDOS AutoCheckIn 定时自动签到
Stars: ✭ 81 (+8%)
Mutual labels:  github-actions
Actions Openwrt
A template for building OpenWrt with GitHub Actions | 使用 GitHub Actions 云编译 OpenWrt
Stars: ✭ 4,742 (+6222.67%)
Mutual labels:  github-actions
Act
Run your GitHub Actions locally 🚀
Stars: ✭ 19,915 (+26453.33%)
Mutual labels:  github-actions
spec-prod
GitHub Action to build ReSpec/Bikeshed specs, validate output and publish to GitHub pages or W3C
Stars: ✭ 19 (-74.67%)
Mutual labels:  github-actions
the-good-place
A GitHub Action that lets you be an architect of your own neighborhood (your repository) in The Good Place
Stars: ✭ 46 (-38.67%)
Mutual labels:  github-actions
Openwrt Rpi
Raspberry Pi & NanoPi R2S/R4S & G-Dock & x86 OpenWrt Compile Project. (Based on Github Action / Daily Update)
Stars: ✭ 3,492 (+4556%)
Mutual labels:  github-actions
nest-boilerplate
Nest.js boilerplate with CircleCI, Commitizen, Commitlint, Docker-Compose, ESLint, GitHub Actions, Husky, Lint-staged, OpenAPI, Prettier, PostGreSQL, Travis CI, TypeORM
Stars: ✭ 16 (-78.67%)
Mutual labels:  github-actions
Awesome Actions
A curated list of awesome actions to use on GitHub
Stars: ✭ 16,943 (+22490.67%)
Mutual labels:  github-actions
angular-forum
Forum application built with Angular
Stars: ✭ 52 (-30.67%)
Mutual labels:  github-actions
Github Pages Deploy Action
Automatically deploy your project to GitHub Pages using GitHub Actions. This action can be configured to push your production-ready code into any branch you'd like.
Stars: ✭ 2,507 (+3242.67%)
Mutual labels:  github-actions
juejin-actions
掘金每天自动签到 github actions 。组织了每周一起学习200行左右的【源码共读】活动,感兴趣可以加我微信 ruochuan12 参与。
Stars: ✭ 47 (-37.33%)
Mutual labels:  github-actions
Cml
♾️ CML - Continuous Machine Learning | CI/CD for ML
Stars: ✭ 2,843 (+3690.67%)
Mutual labels:  github-actions
Actions Gh Pages
GitHub Actions for GitHub Pages 🚀 Deploy static files and publish your site easily. Static-Site-Generators-friendly.
Stars: ✭ 2,576 (+3334.67%)
Mutual labels:  github-actions

Github Wiki Publish Action

This GitHub Action publishes the contents of a directory to your project's wiki from a workflow.

Usage

In a new or existing workflow, add a step using SwiftDocOrg/github-wiki-publish-action@v1 with a path to a directory containing the documentation you wish to upload.

name: Documentation

on: [push]

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v1
      # Additional steps to generate documentation in "Documentation" directory
      - name: Upload Documentation to Wiki
        uses: SwiftDocOrg/github-wiki-publish-action@v1
        with:
          path: "Documentation"
        env:
          GH_PERSONAL_ACCESS_TOKEN: ${{ secrets.GH_PERSONAL_ACCESS_TOKEN }}

Supported Products

  • GitHub.com
  • GitHub Enterprise Cloud
  • GitHub Enterprise Server
  • GitHub AE

Setup

This GitHub action requires that your repository has the following:

  • A wiki with at least one page in it
  • A secret named GH_PERSONAL_ACCESS_TOKEN with a Github personal access token with "repo" authorization

Follow the steps below to ensure that everything's configured correctly.

Note GitHub doesn't currently provide APIs for interacting with project wikis, so much of the required setup must be done manually.

1. Enable Your Repository's Wikis Feature

Navigate to the "Settings" tab for your repository, scroll down to the "Features" section, and ensure that the checkbox labeled "Wikis" is checked.

GitHub Wikis Feature

2. Create the First Wiki Page

With the Wikis feature enabled for your repository, navigate to the "Wiki" tab. If prompted, create the first wiki page.

GitHub Wiki Create First Page

3. Generate a Personal Access Token

Navigate to the Personal access tokens page in your GitHub account settings (Settings > Developer settings > Personal access tokens) and click the "Generate a new token" button.

In the "New personal access token" form, provide a descriptive comment in the "Note" field, like "Wiki Management". Under "Select scopes", enable all of the entries under "repo" perms.

When you're done, click the "Generate token" button at the bottom of the form.

GitHub Personal Access Token Select Scopes

Note: GitHub actions have access to a GITHUB_TOKEN secret, but that token's permissions are limited to the repository that contains your workflow. This workflow requires the generation of a new personal access token to read and write to the git repository for your project's wiki.

4. Set a Repository Secret

Copy your generated personal access token to the clipboard and navigate to your project settings. Navigate to the "Secrets" page, click "Add a new secret", and fill in the form by entering GH_PERSONAL_ACCESS_TOKEN into the "Name" field and pasting your token into the "Value" field.

License

MIT

Contact

Mattt (@mattt)

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].