spectrocloud / librarium

Spectro Cloud documentation
https://docs.spectrocloud.com
17 stars 34 forks source link

ci: migrate to Vale #3233

Closed karl-cardenas-coding closed 1 week ago

karl-cardenas-coding commented 1 week ago

Describe the Change

This PR migrates the repository to use the internal Vale package.

Backports

Can this PR be backported?

netlify[bot] commented 1 week ago

Deploy Preview for docs-spectrocloud ready!

Name Link
Latest commit cb603b87ec29efcf063309eb5f7e5bd5ed5f39f7
Latest deploy log https://app.netlify.com/sites/docs-spectrocloud/deploys/668444b53c9159000839352e
Deploy Preview https://deploy-preview-3233--docs-spectrocloud.netlify.app
Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

vault-token-factory-spectrocloud[bot] commented 1 week ago

💔 Some backports could not be created

Status Branch Result
version-4-0 Backport failed because of merge conflicts

You might need to backport the following PRs to version-4-0:
- ci: added missing condition for non-cron workflows (#1720)
- ci: changed default workflow
version-3-4 Backport failed because of merge conflicts

You might need to backport the following PRs to version-3-4:
- ci: added missing condition for non-cron workflows (#1720)
- ci: changed default workflow
- chore: released docs versioning
- docs: palette-cli URL update
version-4-1 Backport failed because of merge conflicts

You might need to backport the following PRs to version-4-1:
- ci: updated vale configuration (#2335)
- ci: added missing condition for non-cron workflows (#1720)
- ci: changed default workflow
version-4-2 Backport failed because of merge conflicts
version-4-3 Backport failed because of merge conflicts
version-4-4

Note: Successful backport PRs will be merged automatically after passing CI.

Manual backport

To create the backport manually run:

backport --pr 3233

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details