-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
remove: asyncapi-plugin-idea #67
Comments
Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request. |
Will discuss the transfer date later. I plan to make it done by end of the year |
IDEA plugins for now has own release cycles and can't live here anymore. asyncapi#67
sure, so it basically means that code for the plugin must have a standalone repo? wouldn't it be better to start in asyncapi org directly? |
Yes
I already moved the plugin to new repo ~6 months ago |
…api-plugin-idea IDEA plugins for now has own release cycles and can't live here anymore. asyncapi#67
This issue has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation. There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
IDEA plugins for now has own release cycles and can't live here anymore.
Remove
asyncapi-plugin-idea
fromasyncapi-plugin
.Till transfer to AsyncAPI repo plugin lives in my repository: https://github.com/Pakisan/jasyncapi-idea-plugin
The text was updated successfully, but these errors were encountered: