Update Namecheap status #3604
Merged
Update Namecheap status #3604
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
ldez
added
kind/enhancement
|
Just a heads up to @stoinov , I finally have namecheap API access. I gonna test either tonight or tommorow :) |
SantoDE
approved these changes
Jul 23, 2018
|
Changing to 1.7 base |
dtomcej
added
status/3-needs-merge
and removed
bot/no-merge
status/2-needs-review
labels
dtomcej
added
bot/light-review
dtomcej
removed
the
bot/light-review
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 does this PR do?
I updated the status of Namecheap for the DNS challenge
Motivation
I tested and was able to use the DNS challenge for a wildcard certificates with Namecheap
More