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

Build docs using GitHub Actions, add linkcheck, and small tweaks to CI system #232

Merged
merged 8 commits into from
Dec 20, 2021

Conversation

yuvipanda
Copy link
Contributor

CircleCI isn't building repos on merge anymore
for some reason. Instead of debugging it, I'm just going to
give more power to one particular huge corporation (Microsoft)
and move our docs build to GitHub Actions as well.

Fixes #227

Copy link
Member

@consideRatio consideRatio left a comment

Choose a reason for hiding this comment

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

Thanks for making this happen!!

if: github.ref == 'refs/heads/main'
run: |
pip install ghp-import
ghp-import --no-jekyll --push --message "Update documentation [skip ci]" docs/_build/html
Copy link
Member

@consideRatio consideRatio Nov 16, 2021

Choose a reason for hiding this comment

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

I wonder if we will have a github user configured to indicate this is a bot, otherwise the git user will be of the person that triggered the workflow - which would be whoever pushed / merged a PR i think. That is probably acceptable as well though.

I'm not sure how ghp-import --push works.

Copy link
Member

@consideRatio consideRatio Nov 16, 2021

Choose a reason for hiding this comment

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

It seems like they have no configuration about setting the git user to make the commit, so I assume its done with the current user without modification of that etc.

https://pypi.org/project/ghp-import/

In z2jh we have explicitly set an author when we make a commit for example: https://github.com/jupyterhub/zero-to-jupyterhub-k8s/blob/04de3447397bb85b495d0302984d36c61bc75da5/.github/workflows/vuln-scan.yaml#L204

@yuvipanda
Copy link
Contributor Author

Thank you for the comments, @consideRatio! Unfortunately I don't have time right now to push this through, would love for someone else to take this over.

@consideRatio consideRatio marked this pull request as ready for review December 18, 2021 13:38
Copy link
Member

@consideRatio consideRatio left a comment

Choose a reason for hiding this comment

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

This LGTM as it now is!

I added linkchecks and fixed a link that had a broken anchor according to the linkcheck, note that I changed the destination to point to the chrome web store instead of the manual installation guide for chrome as part of doing this!

@yuvipanda what do you think?

@consideRatio consideRatio changed the title Move docs building workflow to GitHub Actions Build docs using GitHub Actions, add linkcheck, and small tweaks to CI system Dec 18, 2021
@yuvipanda yuvipanda merged commit d22c66b into jupyterhub:main Dec 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Docs site not updating
2 participants