The RN OMH Maps repository do not have a separate task to publish documentation, similar to the one found here. I created a quick workaround in the react-native-omh-auth repository, but it required changes in the turbo.json file, specifically modifying pipelines to tasks.
Expected Behavior
A separate task should exist to handle the publishing of documentation for RN OMH Auth, similar to other repositories.
Steps to Reproduce
Check the current workflow configuration in the RN OMH Auth repositories.
Notice the lack of a separate task for publishing documentation.
Workaround
I made changes in the react-native-omh-auth repository by:
Creating a new workflow file: .github/workflows/build-publish-docs.yml
Modifying turbo.json:
Changed pipelines to tasks to address the issue.
Proposed Solution
Create a separate task for publishing docs in RN OMH Maps and Auth repositories.
Ensure the task is similar to the one referenced above to maintain consistency across repositories.
Additional Context
Natalia & Andrei - This issue reflects a recurring problem that should have been addressed based on our previous experience. Why are we repeating the same issues? A collective approach to streamline documentation publishing tasks across all repositories would prevent these repetitive fixes. Esp. when it's the same team working across the same modules.
Please address this issue to maintain a streamlined workflow for documentation publishing.
The RN OMH Maps repository do not have a separate task to publish documentation, similar to the one found here. I created a quick workaround in the react-native-omh-auth repository, but it required changes in the
turbo.json
file, specifically modifyingpipelines
totasks
.Expected Behavior
A separate task should exist to handle the publishing of documentation for RN OMH Auth, similar to other repositories.
Steps to Reproduce
Workaround
I made changes in the
react-native-omh-auth
repository by:.github/workflows/build-publish-docs.yml
turbo.json
:pipelines
totasks
to address the issue.Proposed Solution
Additional Context
Natalia & Andrei - This issue reflects a recurring problem that should have been addressed based on our previous experience. Why are we repeating the same issues? A collective approach to streamline documentation publishing tasks across all repositories would prevent these repetitive fixes. Esp. when it's the same team working across the same modules.
Please address this issue to maintain a streamlined workflow for documentation publishing.