-
Notifications
You must be signed in to change notification settings - Fork 12
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 breaking changes from starter-pack and improve workflow #220
Conversation
68baf05
to
bc7d3a3
Compare
bc7d3a3
to
3130e9b
Compare
- There are recent breaking changes in canonical/sphinx-docs-starter-pack that causes our workflow to fail. Updated those changes in COU to align. - Update the workflow to only trigger documentation checks if a PR modifies `docs/`. This will prevent un-necessary runs. I'm keeping the on.push as is because I think it is good to have a way to notify us about dependency breakage (those issues are not affecting live doc site).
3130e9b
to
201e713
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally, LGTM. I'm wondering if it would be good or possible to have in our Makefile a option to sync with the upstream documentation as it happens for example on charm-helpers on classic charms.
@gabrielcocenza Right now there's no clean way to automate the upstream tracking because we are modifying the files from starter-pack. Documentation team is aware of the limitation and will work on supporting such an automation. But until then, there's nothing we can do from our side. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
docs/
. This will prevent un-necessary runs. I'm keeping the on.push as is because I think it is good to have a way to notify us about dependency breakage (those issues are not affecting live doc site).