-
Notifications
You must be signed in to change notification settings - Fork 3
How to get verified status on a module #81
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
Comments
I see what you're referring to and will look into it today. |
For verification, I guess, A coder user should first manually test them, and the module should have automatic tests (if applicable). |
@stirby, now we have module versioning. Do you think having automated tests is enough to put a verified badge on a module? |
@matifali We can verify modules with tests, but we should update the readme to reflect this. We should also mention that the module creator is responsible for maintenance if that's the policy we're going with. |
@stirby I am ok with this. This can go in our CONTRIBUTING.md file. |
Hi @masterwendu, could you update the maintainer GitHub to your GitHub account instead of @WhizUs |
Hi, |
Hi,
I created the 2 exoscale modules for the registry.
I set verified to
false
because I wasn´t sure how to verify.Is is possible to verify a module?
Moreover you have a bug on the registry website.
In the modules overview our exoscale modules are not verified.
But in the detailed module view it is. It seems that you set a condition wrong there.
The text was updated successfully, but these errors were encountered: