Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update repo wiki page based on docs #3069

Open
wants to merge 10 commits into
base: main
Choose a base branch
from
44 changes: 44 additions & 0 deletions .github/workflows/wiki.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
name: Publish Wiki

# Trigger this action only if there are changes pushed to the wiki/** directory under the main branch
on:
push:
paths:
- docs/** # This includes all sub folders
branches:
- main # This can be changed to any branch of your preference

env:
USER_TOKEN: <USER_TOKEN_ENV_VARIABLE> # This is the repository secret
USER_NAME: <USER_NAME> # Enter the username of your (bot) account
USER_EMAIL: <USER_EMAIL> # Enter the e-mail of your (bot) account
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do these need to be filled out with anything?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes they do, for the CI to run, there needs to be the environment variable for the user token secret, kind of like secrets.GITHUB_TOKEN that you have in release.yml workflow.
for the name and email, those are for the commits, so we can see in the wiki where the updates come from. It usually shows as "revisions".

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for getting to this so late. So I need to change those myself? Or can you do it in this PR?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't really know which secret to use to access the wiki, so what I did for now is I changed them to these

env:
  USER_TOKEN: ${{ secrets.WIKI_TOKEN }}
  USER_NAME: github-actions[bot]
  USER_EMAIL: github-actions[bot]@users.noreply.github.com

I cannot really use the same GITHUB_TOKEN you use in the other workflows because the wiki is technically a different repository, so the secret for this repository won't work for it as far as I know, so I just put a WIKI_TOKEN.

Now what you need to do for this to work (hopefully if I didn't miss anything):

  1. Go to GitHub Settings → Developer Settings → Personal Access Tokens
  2. Generate a new token with wiki permissions
  3. Add it to your repository's secrets as WIKI_TOKEN

OWNER: ${{ github.event.repository.owner.login }} # This is the repository owner
REPOSITORY_NAME: ${{ github.event.repository.name }} # This is the repository name

jobs:
publish_wiki:
name: Publish wiki
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v3

- name: Pull content from wiki
run: |
mkdir tmp_wiki
cd tmp_wiki
git init
git config user.name $USER_NAME
git config user.email $USER_EMAIL
git remote add origin https://[email protected]/$OWNER/$REPOSITORY_NAME.wiki.git
git fetch origin
git checkout master || git checkout -b master
git pull origin master

- name: Push content to wiki
run: |
rsync -av --delete docs/ tmp_wiki/ --exclude .git
cd tmp_wiki
git add .
git commit -m "Update Wiki content" || echo "No changes to commit"
git push origin master
10 changes: 8 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -123,12 +123,18 @@ As of v0.21.0, chaiNNer uses our new package called [Spandrel](https://github.co

## Troubleshooting

For troubleshooting information, view the [troubleshooting document](docs/troubleshooting.md).
For troubleshooting information, view the [troubleshooting document](https://github.com/chaiNNer-org/chaiNNer/wiki/06--Troubleshooting).

## Building chaiNNer Yourself

I provide pre-built versions of chaiNNer here on GitHub. However, if you would like to build chaiNNer yourself, simply run `npm install` (make sure that you have at least npm v7 installed) to install all the nodejs dependencies, and `npm run make` to build the application.

## FAQ

For FAQ information, view the [FAQ document](docs/FAQ.md).
For FAQ information, view the [FAQ document](https://github.com/chaiNNer-org/chaiNNer/wiki/07--FAQ).

## Documentation

For in-depth documentation covering various aspects of ChaiNNer, including CLI usage, data representation, and a contributor's guide, kindly refer to our [ChaiNNer Wiki](https://github.com/chaiNNer-org/chaiNNer/wiki).


File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
27 changes: 27 additions & 0 deletions docs/Home.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
# Welcome to the ChaiNNer Wiki !

This wiki serves as a comprehensive guide to ChaiNNer, a visual programming language and development environment for chaining image processing tasks together. Below are the key sections of the documentation:

## Table of Contents

**[[01--Contributing]]** - *Overview of how to contribute to the ChaiNNer project, with setup instructions and project structure.*

**[[02--Data-Representation]]** - *Details on how ChaiNNer handles various data types such as images, text, and numbers, along with conventions for node implementations.*

**[[03--Nodes]]** - *Information about nodes in ChaiNNer, covering their structure, rules, and methods for implementation.*

**[[04--Navi]]** - *Overview of the Navi type system used for static validation and real-time feedback in ChaiNNer.*

**[[05--CLI]]** - *Instructions for operating ChaiNNer in command-line interface mode, allowing for chain execution without a GUI.*

**[[06--Troubleshooting]]** - *Solutions to common issues encountered while using ChaiNNer, addressing installation and runtime problems.*

**[[07--FAQ]]** - *Answers to frequently asked questions about ChaiNNer, including feature requests and usage scenarios.*

## Additional Resources

For more information, check out the individual sections linked above. If you have any questions or need further assistance, feel free to reach out to the community in [discord](https://discord.gg/pzvAKPKyHM) or [open an issue](https://github.com/chaiNNer-org/chaiNNer/issues) on the GitHub repository.

---

Thank you for visiting the ChaiNNer wiki!