community VS gitlab

Check out how to create your own or feel free to borrow from Community Discussions’ templates.

Although GitHub did not have a plan to support this option, but AzureDevops and GitLab already supported this. https://github.com/community/community/discussions/8940 You can manually do it for now

[4]: https://github.com/community/community/discussions/37117

I think it's not about missing commands, but missing destination (package repo of "generic" type). Very same issue posted here: https://github.com/community/community/discussions/38083

btw - I know this exists, but it seems like the posts are responded to much: https://github.com/community/community/discussions/categories/copilot

It appears that you're using IPv6 (your ping is returning IPv6 addresses). A quick search shows some github services may not support IPv6 but that's just a guess

Yeah, Vundle's (presumably temporary) removal caught me off guard today on a fresh install. This, in turn, has caused me to take a hard look at the Vim plugins I was using. Turns out I only needed one...which I wrote. So I'm now just storing that one in the horrible "vanilla" Vim plugin scheme and putting that in my dotfile management.

Just a good reminder that dependencies will always let you down. It's just a matter of time. Oh, and never turn your back on a big company.

Here's the tracking on this issue:

https://github.com/community/community/discussions/48173

GitHub: "The VundleVim organization has been flagged. Because of that, your organization is hidden from the public."

It's a relatively new beta feature for GitHub.

Here's the support discussion ticket for this:

https://github.com/community/community/discussions/48173

>The VundleVim organization has been flagged.

Since the relevant code appears to be in the "ee" directory <https://gitlab.com/gitlab-org/gitlab/-/blob/v16.11.0-ee/ee/l...> and is not present in the foss repo, I'm guessing the answer is no, at least for now. They do have a history of "releasing" features from EE back to CE but my suspicion is not for LLM stuff

(Side note: Issues are usually hash-prefixed like #1234 both on GitLab and GitHub. However, commit messages must not begin with a hash, they would be considered a comment and ignored. Therefore, GitHub has introduced the alternative prefix GH- and I've contributed a similar prefix GL- to GitLab a while ago.)

and its "oh, you want multi-arch, do you?" friend. While prosecuting this <https://gitlab.com/gitlab-org/gitlab/-/issues/339567> I learned that https://hub.docker.com/layers/multiarch/qemu-user-static/7.2... actually mutates the binfmt_misc in buildx's context in order to exec the static copy of qemu in it https://github.com/multiarch/qemu-user-static/blob/v7.2.0-1/...

and, that the buildx plugin itself has some qemu magick in it, which got addressed in a minor version bump but I couldn't track down the relevant GitHub issue this second (I've flushed it from my mind, only recalling that there were a lot of actors in that tire fire)

This is actually a follow-up refactor, the fix is here: https://gitlab.com/gitlab-org/gitlab/-/commit/abe79e4ec43798...