-
-
Notifications
You must be signed in to change notification settings - Fork 24
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #32 from d3vadam/patch-1
Changes to FAQ.
- Loading branch information
Showing
1 changed file
with
9 additions
and
3 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -12,11 +12,14 @@ We support the following records: | |
## Why does my domain still redirect to the is-a-dev website? | ||
This usually occurs due to the cache of your browser becoming invalid and [clearing your browser's cache](https://support.google.com/accounts/answer/32050) should solve this issue. | ||
|
||
## Can I use a CNAME record with any other records? | ||
You cannot request a subdomain nor submit changes containing a CNAME with any other records (TXT, A, MX, etc...) | ||
|
||
## How long will it take for my PR to get merged? | ||
When we get into it. We always want you to wait for as short as possible. But maintainers cannot always be online. We have school and work, this is just a side project. Just be patient and we'll get to it as soon as possible! For a chance for a quicker review, send your PR in [pull-requests](https://discord.com/channels/830872854677422150/1130858271620726784). | ||
|
||
## Which services do you support? | ||
We support almost all services except Vercel. For example: Github Pages and Cloudflare Pages. | ||
We support almost all services except Vercel. For example: GitHub Pages and Cloudflare Pages. | ||
|
||
## Can I create nested subdomains? (sub-sub domains) | ||
Yes, you can! Simply create a file such as `blog.example.json` and follow the same guidelines as you would while registering `example.json`. Please note in order to have `blog.example.is-a.dev`, you must also own `example.is-a.dev`. | ||
|
@@ -27,11 +30,14 @@ You can edit your domain's JSON file and submit a pull request to edit your doma | |
## How can I delete my domain? | ||
You can delete your domain's JSON file and submit a pull request to delete your domain. | ||
|
||
## I keep getting a SSL error while using GitHub Pages, how do i fix this? | ||
You need to go to your GitHub Pages settings on your website repository (likely called `<user.github.io>`) and make sure the `Enforce HTTPS` option is enabled to avoid this error. | ||
|
||
## Can I be a maintainer/join the team? | ||
No, we handpick every member of our team. You can increase your chances of being chosen by helping out people in our help forums. | ||
|
||
## I have accidentally leaked sensitive information in my PR, how can I get my PR deleted? | ||
If your PR **has not been merged**, you can DM [William](https://discord.com/users/853158265466257448) however, if it has been merged already, then there is nothing we can do about it unfortunately. | ||
If your PR **has not been merged**, you can email [[email protected]](mailto:[email protected]) or DM [williamharrison on Discord](https://discord.com/users/853158265466257448) however, if it has been merged already, then there is nothing we can do about it unfortunately. | ||
|
||
## My DNS records are not updating even after 48 hours, what should I do? | ||
Please open a help thread via any of our help channels and we will look into it. | ||
|
@@ -53,4 +59,4 @@ Sure, but it needs to be a nested subdomain (mc.example.is-a.dev). You would nor | |
|
||
1. **Wait for your PR to be merged:** After you have submitted your pull request, wait for it to be reviewed and merged. Once your pull request has been merged, your changes should be live! | ||
|
||
**Note:** Make sure to monitor your PR for reviews in case some changes are requested. Also note that it can take up to 48 hours in some rare cases for your changes to take effect after your PR is merged. | ||
**Note:** Make sure to monitor your PR for reviews in case some changes are requested. Also note that it can take up to 48 hours in some cases for your changes to take effect after your PR is merged. |