Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
community
Public feedback discussions for: GitHub Mobile, GitHub Discussions, GitHub Codespaces, GitHub Sponsors, GitHub Issues and more! (by community)
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Not sure if Vundle did anything particularly fancy, but I'm using vim-plug [0] and have no complaints. It stays out of my way to the point that I had to look at my .vimrc just now to make sure that's what I was using.
[0] https://github.com/junegunn/vim-plug
Seems to have ben cloned 3 hours ago [0], i don't know if this code is the originial, as i've never used it before but a quick search gave me this repo.
[0]https://github.com/mckellygit/Vundle.vim
"The VundleVim organization has been flagged"[1] --- the author seems to be puzzled as well.
[1] https://github.com/community/community/discussions/48173
Here is a recent copy of the official repo
https://github.com/wgallios/Vundle.vim
I’ve found two useful forks - one unmodified [0], the other one just with a README update [1].
Because those are actual GitHub forks (instead of just re-uploads of a local clone), they’re technically still connected to the original repository on GitHub, including the latest commit [2] of the original before it went down.
[0]: https://github.com/houbaiding/vim-Vundle.vim