-
Notifications
You must be signed in to change notification settings - Fork 3
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
🎉 Back to trunk! 🎉 #21
Comments
Trunk 0.18.0 has been released. It contains the changes of trun-ng and it the way forward. |
You might want to put this somewhere more visible than a closed issue, like in the project description or readme file? Took me more than a good minute to figure out that trunk-ng was deprecated by finally finding this. Oh, not to mention the link to the organization in the OP is broken. 😅 |
Fixed the link, thanks! Kind of tricky. It's the only pinned issue. I was hoping that's good enough. Putting that in the readme doesn't work, as that's the readme of the trunk (proper) repository. I updated the link of the "homepage", pointing to https://github.com/trunk-rs/trunk/ |
But this is a fork? Changes made here don't happen there... right? 🤔 |
Yes, it's a fork. But a "traditional" upstream fork. So |
Trunk now has it's own organization: https://github.com/trunk-rs and
trunk-ng
is merged back intotrunk
.I think that's the best outcome we could have. And it makes this organization obsolete.
So, I will move this organization's
trunk
repository back to my personal space in the near future. All future development should happen intrunk-rs
.The text was updated successfully, but these errors were encountered: