We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
While providing sample plugins is very nice to detail how to use each of the API - we should not be showing that by default to the end users.
When creating a new workspaces / or editing an existing ones, the users will want to configure real plugins only.
When the user is creating a workspaces for Che in Che development or Plugin developemnt, we should be showing those plugins in the samples.
The text was updated successfully, but these errors were encountered:
We should remove the sample plugins from the registry and add them as samples for the che in che stack. Is it right @slemeur?
Sorry, something went wrong.
Yes sounds good ! thanks @l0rd
No branches or pull requests
Description
While providing sample plugins is very nice to detail how to use each of the API - we should not be showing that by default to the end users.
When creating a new workspaces / or editing an existing ones, the users will want to configure real plugins only.
When the user is creating a workspaces for Che in Che development or Plugin developemnt, we should be showing those plugins in the samples.
The text was updated successfully, but these errors were encountered: