You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi everyone! I am looking for maintainers of this repository, since personally I may long unresponsive which can harm this community.
It probably won't cost you too much time, please state your interest, you will be invited as a collaborator and I myself will still continue to contribute to this project.
@felipecrs I'll do it when the pipeline for #283 was done on the main branch.
There are still some pending actions. For example the vscode marketplace publisher. We may need to create a new publisher (org publisher), however I haven't find an easy way to migrate publisher transparently for end users.
There are still some pending actions. For example the vscode marketplace publisher. We may need to create a new publisher (org publisher), however I haven't find an easy way to migrate publisher transparently for end users.
Activity
felipecrs commentedon Aug 2, 2021
Hey @timonwong! I think it may be a good time to move the project to the its own org that you created at https://github.com/vscode-shellcheck. What do you think?
https://docs.github.com/en/github/administering-a-repository/managing-repository-settings/transferring-a-repository#transferring-a-repository-owned-by-your-user-account
timonwong commentedon Aug 3, 2021
@felipecrs I'll do it when the pipeline for #283 was done on the main branch.
There are still some pending actions. For example the vscode marketplace publisher. We may need to create a new publisher (org publisher), however I haven't find an easy way to migrate publisher transparently for end users.
felipecrs commentedon Aug 3, 2021
I think this cannot be made at all. For example we have https://github.com/microsoft/eslint-vscode which still publishes as dbaeumer.vscode-eslint for the same reason.