Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Move into `EmmyLuaLs` GH Organization ?

Open
  • Is something wrong?
#319 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
rust, typescript, vscode
Domain
devops, documentation, release

Research direction

No source files or tests are named. Start by reviewing the GitHub repository ownership settings, then check the VS Code Marketplace, Open VSX Registry, emmylua.github.io, and emmylua-analyzer-rust references to identify migration dependencies; done means the repository is moved without breaking redirects and the affected ownership and release details are coordinated.

Written by the indexing model from the issue text.

Description

As for now, there are 2 organizations:

This is "slightly" (actually huge) confusing for everyone — both users and contributors.
I got confused myself by all these versions/copies/variants.

I suggest making the first small step towards unification:

  • Move this repository to EmmyLuaLs.
    In fact, this extension already uses the new emmylua_ls, which is located in emmylua-analyzer-rust, which is hosted under the EmmyLuaLs organization.
    • No Breaking Changes: GitHub automatically handles redirects for the repository URL, clones, stars, and forks,.. so on...

The migration will solve several problems:

  1. Unified Naming & Publishers (Marketplace / Open VSX)
    The naming and publishers situation is currently a mess: in the VS Code Marketplace, the extension is under the personal account of tangzx (tangzx.emmylua), related plugins (like EmmyLuaCodeStyle) are under CppCXY, and on Open VSX, third parties are publishing their own forks (like theo.emmylua or xuhuanzy.emmylua-luals).
    Consolidating under EmmyLuaLs is the perfect opportunity to set up official, unified organization publishers/namespaces (e.g., emmyluals.emmylua) across the MS Marketplace, Open VSX Registry, and so on... This ensures brand safety, ownership continuity, and trust.

  2. The Documentation Mess
    The documentation issue is critical: right now, the old emmylua.github.io website is hosted by the old organization and leads to the Java version, while the docs for the new Rust version are hidden deep inside the emmylua-analyzer-rust repository.
    Moving the repo to EmmyLuaLs will help users understand that it's all part of the same project, and they will actually know what is relevant for the modern extension.

[!NOTE]
Here also I would like to help to make new modern website with docs. (something like our: https://voxrame.dev/ , https://voxrame.dev/utils/helpers , but in Emmy Style ) -- with search through docs/annotations/..., with translations into several languages, and so on...

  1. Scattered Issue Tracking
    Users frequently open issues regarding the Rust language server directly in this VSCode-EmmyLua repository just because it's the client they use. Having them in separate organizations makes triaging and transferring issues between the extension and the core LSP server unnecessarily annoying.

  2. CI/CD and Release Automation
    Additionally, this will allow us to easily build a streamlined CI/CD pipeline where an update or a tag in the Rust LSP core can automatically trigger automated testing or a release candidate preview for the VSCode extension.

PS: cant register in QQ. :( @CppCXY , have you Discord ? (cc: @tangzx)

Dominant language
TypeScript
Stars
753
Forks
114
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EmmyLua/VSCode-EmmyLua

All issues in EmmyLua/VSCode-EmmyLua

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.