Closed canerakdas closed 4 months ago
The latest updates on your projects. Learn more about Vercel for Git âïž
Name | Status | Preview | Updated (UTC) |
---|---|---|---|
nodejs-org | â Ready (Inspect) | Visit Preview | Jun 3, 2024 8:45pm |
Lighthouse Results URL | Performance | Accessibility | Best Practices | SEO | Report |
---|---|---|---|---|---|
/en | ð 76 | ð¢ 100 | ð¢ 96 | ð¢ 91 | ð |
/en/about | ð¢ 98 | ð¢ 100 | ð¢ 96 | ð¢ 91 | ð |
/en/about/previous-releases | ð¢ 98 | ð¢ 100 | ð¢ 100 | ð¢ 92 | ð |
/en/download | ð¢ 99 | ð¢ 100 | ð¢ 100 | ð¢ 91 | ð |
/en/blog | ð¢ 100 | ð¢ 100 | ð¢ 96 | ð¢ 92 | ð |
Is it still a WIP?
@canerakdas can you make the changes to the GitHub Action Workflow on a separate PR so I can merge it first?
Is it still a WIP?
The last build failed, so I marked it as WIP. I'm trying to understand the problem ð€
@canerakdas can you make the changes to the GitHub Action Workflow on a separate PR so I can merge it first?
Sure, I will open it as a separate PR after solving this problem ð
Is it still a WIP?
The last build failed, so I marked it as WIP. I'm trying to understand the problem ð€
@canerakdas can you make the changes to the GitHub Action Workflow on a separate PR so I can merge it first?
Sure, I will open it as a separate PR after solving this problem ð
After solving what problem? You know changes to the workflow only take effect after merging.
So Imo the workflow change should fix this, but we can only test that after you merge the workflow changes ð
After solving what problem? You know changes to the workflow only take effect after merging.
So Imo the workflow change should fix this, but we can only test that after you merge the workflow changes ð
Updated :smile: I'd better get some rest, I'm starting to see non-existent issues ð»
Fast-tracking this to see if it fixes the upload!
Description
With this PR, we aim to solve the Orama cloud sync issue mentioned in #6719
Related Issues
Related to #6719