no output saved in a forked manuscript

[aseedb]

no output saved in a forked manuscript

[dhimmel]

Skipping deployment in forks is intentional, since often forks don't want a distinct HTML page. You can change this setting at

rootstock/.github/workflows/manubot.yaml

Lines 94 to 95 in 9504aa7

	- name: Deploy Manuscript
	if: github.ref == env.DEFAULT_BRANCH_REF && github.event_name != 'pull_request' && !github.event.repository.fork

Remove && !github.event.repository.fork

[aseedb]

Thank you guys for your support. @dhimmel your solution solved my problem.

[agitter]

Can you confirm that the "Deploy Manuscript" step of the GitHub Actions workflow ran? If it did, then I would next check the GitHub Pages setup. Perhaps that doesn't work automatically when forking a repo.

Following this setup step

try reselecting "gh-pages branch" as the Source for GitHub Pages in the repository Settings. GitHub Pages should now trigger on the next commit.

[aseedb]

It did not execute the deploy (see picture)

I forgot to say that the repo is private. Could this be the reason? If not then i try the full setup