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
In the Slack post David Read mentions that we shouldn't be using the crown logo in our docs - we should keep an eye on whether the issue he raised with CDDO has been addressed before implementing the ticket.
Proposal / Unknowns
Definition of Done
Any breaking changes been reviewed to assess any remediation required
Remediation completed and version updated
Testing completed successfully
Another team member has reviewed
The text was updated successfully, but these errors were encountered:
From what I've seen this should be fairly simple. Bump the version and then swap this:
- name: Compile Markdown to HTML and create artifact
run: |
/scripts/deploy.sh
For this:
- name: Compile Markdown to HTML and create artifact
run: |
/usr/local/bin/package
But it's probably worth us looking at how AP publish their docs as a comparator. For example, pulling the lychee job into our process for building the docs
User Story
As a MP engineer
I want to update the tech docs github page publisher to the latest version
So that the platforms dependencies are kept up to date
Value / Purpose
The tech docs github page publisher has had a major upgrade (v4.0.0). We need to review the breaking changes and update to the latest version.
For more information see this Slack post
We make use of this in the publish-gh-pages repo
Useful Contacts
No response
Additional Information
In the Slack post David Read mentions that we shouldn't be using the crown logo in our docs - we should keep an eye on whether the issue he raised with CDDO has been addressed before implementing the ticket.
Proposal / Unknowns
Definition of Done
The text was updated successfully, but these errors were encountered: