Add workflow to publish Wiki pages

[toby-thanathip]

Why

We want to start adding more to our Wiki section, but GitHub doesn't support creating pull requests for Wiki pages by default. As we want our Wiki pages to be reviewed before being published, we can make use of this GitHub Action.

Basically the idea is as following:

• Add workflow for publishing Wiki pages (Ex: wiki.yml)
• Add markdown files that represents the Wiki content (Ex: Campaign.md)
• Set environment variables (Ex: GH_PAT)

When merging to main, then we publish all markdown files to the Wiki section

name: Publish wiki

on:
  push:
    branches:
      - main

jobs:
  publish:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2
      with:
        ref: ${{ github.ref }}
    - uses: Decathlon/[email protected]
      env:
        GH_PAT: ${{ secrets.WIKI_ACTION_TOKEN }}
        ACTION_MAIL: [email protected]
        ACTION_NAME: team-nimblehq
        OWNER: nimblehq
        REPO_NAME: android-templates
        MD_FOLDER: .github/wiki
        WIKI_PUSH_MESSAGE: Push from Github action

Read more: slides

Who Benefits?

@nimblehq/android-chapter

[toby-thanathip]

@lydiasama What do you think? 🙏

[luongvo]

LGTM @Tuubz 👍

[toby-thanathip]

Sadly this GitHub action has some limitations:

• No support for removing Wiki pages with pull requests: issue
• We can't reference images with a relative path

So I'm planning to merge this and this to a solution of our own 🚀

[lydiasama]

So we will show the wiki after we do release, not every merge that pull request to develop, right? Because we trigger the action once merge to main. @Tuubz

[toby-thanathip]

@lydiasama Oh, I thought we were only making use of main

Looking at the current PR's, they all have main set as the target branch

Please correct me if I'm wrong 🙇

---

Anyhow, we can choose on what branch it should trigger the action 🚀

[toby-thanathip]

@lydiasama Ok, I found the thread!

[toby-thanathip]

So we will show the wiki after we do release, not every merge that pull request to develop, right?

Sounds good to me, let's trigger it on main branch only 🚀