Voxtype repo history rewrite - action required for forks/clones #38
Replies: 4 comments 10 replies
-
|
Yes makes perfect sense. No issues my end. |
Beta Was this translation helpful? Give feedback.
-
|
makes sense, I only have the pending pull request, nothing new. |
Beta Was this translation helpful? Give feedback.
-
|
With Voxtype included in the Omarchy 3.3.0 release, we started seeing a big uptick in interest, so I accelerated this plan and have completed the force-push. |
Beta Was this translation helpful? Give feedback.
-
|
@peteonrails now that you have deleted the local arch install script what is your prefered way of building and installing a dev version? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
First, thank you SO much for your contributions and feedback.
I'm cleaning up the voxtype repository to remove ~650MB of release binaries that were committed to git history. These binaries are already available on GitHub Releases, so storing them in the repo was redundant and causing slow clones.
What's happening:
If you have a fork or clone, you'll have to update:
Timeline: Planning to do this within the next few days, but wanted to check with the community first.
Curious to hear your thoughts @materemias @robzolkos @dromanov @emilien-jegou
If you have any uncommitted work or open PRs, please let me know and I'll coordinate timing.
Thanks for your contributions to voxtype!
— Pete
Beta Was this translation helpful? Give feedback.
All reactions