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

Respect the relative path to the fauna-js-repository during doc publication. #324

Merged
merged 1 commit into from
Feb 5, 2025

Conversation

cleve-fauna
Copy link
Contributor

@cleve-fauna cleve-fauna commented Feb 5, 2025

Description

Our deployment workflows have a bug for docs publication.
They attempt to read files using incorrect relative paths.
This change uses the correct relative path; this should enable us to automate docs publishing again.

Motivation and context

We would like to automate docs publishing.

How was the change tested?

The best way to test this is to run the automation.

Screenshots (if appropriate):

N/A

Change types

    • Bug fix (non-breaking change that fixes an issue)
    • New feature (non-breaking change that adds functionality)
    • Breaking change (backwards-incompatible fix or feature)

Checklist:

    • My code follows the code style of this project.
    • My change requires a change to Fauna documentation.
    • My change requires a change to the README, and I have updated it accordingly.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@cleve-fauna cleve-fauna requested a review from a team as a code owner February 5, 2025 19:40
@cleve-fauna cleve-fauna requested a review from jrodewig February 5, 2025 19:42
@cleve-fauna cleve-fauna enabled auto-merge (squash) February 5, 2025 19:43
@cleve-fauna cleve-fauna merged commit 64a6d71 into main Feb 5, 2025
7 checks passed
@cleve-fauna cleve-fauna deleted the main_fixDocPublishing branch February 5, 2025 19:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants