Adding custom domain should go from unverified to verified status
Open
enhancement
- Dominant language
- Python
- Stars
- 563
- Forks
- 410
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 197
Description
Usually in other systems, when adding custom domain, it will capture the entry but will set the status as Unverified. Later it will go to Verified DNS state. Since this involves DNS Propagation, it can go from Unverified status to Verified DNS status rather than showing a warning message like below
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by locating the custom-domain creation and DNS-verification entry points, then verify that a new domain is recorded as Unverified and transitions to Verified DNS after propagation without the warning message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100