tree: 4dfa422cafae3f70b1bc9b76b7868375d1c02db6 [path history] [tgz]
  1. images/
  2. .gitignore
  3. docfx.json
  4. index.md
  5. README.md
  6. toc.yml
docs/README.md

Docs

Preview on fork

When implementing changes to the website on a fork, the GitHub Actions workflow behaves differently.

On a commit to all branches, the rendered static site will be published to GitHub Pages using GitHub Actions. The latest commit is only visible because all publications use the same output location: https://${YOUR_GITHUB_ACCOUNT}.github.io/arrow-dotnet/

You need to configure your fork repository to use this feature:

  1. Enable GitHub Pages on your fork:
    1. Open https://github.com/${YOUR_GITHUB_ACCOUNT}/arrow-dotnet/settings/pages
    2. Select “GitHub Actions” as “Source”
  2. Accept publishing GitHub Pages from all branches on your fork:
    1. Open https://github.com/${YOUR_GITHUB_ACCOUNT}/arrow-dotnet/settings/environments
    2. Select the “github-pages” environment
    3. Change the default “Deployment branches and tags” rule:
      1. Press the “Edit” button
      2. Change the “Name pattern” to * from main or gh-pages

See also the GitHub Pages documentation.