You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
once your configuration is working and you've built your site with ribbity, you can configure your GitHub repository to run ribbity whenever an issue is changed. The simplest way to do this is to use GitHub Actions.
To set up GitHub Actions, add the file https://github.com/ribbity-org/ribbity-docs/blob/main/.github/workflows/ribbity.yml into the .github/workflows directory of your repository. Note that this workflow assumes that your ribbity config file is named site-config.toml and that ribbity runs in the top level directory of your repository.
You will then need to go to settings and under 'Actions', 'General', set your workflow permissions to read and write.
Now, whenever an issue is changed in any way, ribbity will run on the issue tracker and update your Web site.
The text was updated successfully, but these errors were encountered:
ctb
changed the title
automatically run ribbity to update your site using GitHub actions
automatically run ribbity to update your site using GitHub Actions
May 20, 2022
once your configuration is working and you've built your site with ribbity, you can configure your GitHub repository to run ribbity whenever an issue is changed. The simplest way to do this is to use GitHub Actions.
To set up GitHub Actions, add the file https://github.com/ribbity-org/ribbity-docs/blob/main/.github/workflows/ribbity.yml into the
.github/workflows
directory of your repository. Note that this workflow assumes that your ribbity config file is namedsite-config.toml
and that ribbity runs in the top level directory of your repository.You will then need to go to settings and under 'Actions', 'General', set your workflow permissions to read and write.
Now, whenever an issue is changed in any way, ribbity will run on the issue tracker and update your Web site.
The text was updated successfully, but these errors were encountered: