feat: new issue template for provider certification #681
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
salasberryfin
force-pushed
the
issue-template-request-provider-certification
branch
from
870b80f
to
2ff21d1
Compare
Signed-off-by: Carlos Salas <carlos.salas@suse.com>
salasberryfin
force-pushed
the
issue-template-request-provider-certification
branch
from
2ff21d1
to
a30a7ab
Compare
|
Thanks for the comments @furkatgofurov7. PR is updated and ready to be reviewed again. |
alexander-demicev
approved these changes
Aug 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
As part of provider certification, this adds a new issue template for requesting a provider to be added to the list of Certified Providers once it is validated. This can be interesting for certain providers that we're not able to validate ourselves but users may be interested in using. After they certify the providers themselves,they can request it be added to the list and we can decide whether the provider is worth adding the main E2E suite so that it can be added to the Certified Table in the docs.
Which issue(s) this PR fixes:
Fixes #680
Special notes for your reviewer:
Checklist: