commit 196d8a0fe1ea49abfae6991304c10f01ff224d2b
parent e1a8fbe17ad275ca131d3b8ad9a597bad376a65e
Author: iostpa <iostpa@iostpa.com>
Date: Sat, 18 Apr 2026 11:56:53 +0300
v1.1.0: Update the messages and add release workflow
Diffstat:
6 files changed, 61 insertions(+), 14 deletions(-)
diff --git a/.github/workflows/publish-release.yml b/.github/workflows/publish-release.yml
@@ -0,0 +1,43 @@
+name: Publish release docker image
+
+on:
+ push:
+ branches: ['release']
+ paths:
+ - "message/*"
+ - "index.js"
+ - "bun.lock"
+ - "package.json"
+ - "Dockerfile"
+
+jobs:
+ Deploy:
+ runs-on: ubuntu-latest
+ permissions:
+ contents: read
+ packages: write
+ id-token: write
+
+ steps:
+ - name: Checkout Code
+ uses: actions/checkout@v6
+ - name: Set up Docker Buildx
+ uses: docker/setup-buildx-action@v4
+ - name: Login to ghcr.io
+ uses: docker/login-action@v4
+ with:
+ registry: ghcr.io
+ username: ${{ github.repository_owner }}
+ password: ${{ secrets.GHCR_TOKEN }}
+ - name: Extract metadata (tags, labels) for Docker
+ id: meta
+ uses: docker/metadata-action@v6
+ with:
+ images: ghcr.io/${{ github.repository }}
+ - name: Build and Push Docker Image
+ uses: docker/build-push-action@v7
+ with:
+ context: .
+ push: true
+ tags: ${{ steps.meta.outputs.tags }}
+ labels: ${{ steps.meta.outputs.labels }}+
\ No newline at end of file
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -23,6 +23,7 @@ Here are a few things you can do that will increase the likelihood of your pull
- Follow the [style guide][style].
- Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
- Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+- Follow the [Semantic Versioning](https://semver.org/) rules.
## Resources
diff --git a/message/draft.md b/message/draft.md
@@ -5,9 +5,10 @@
You've successfully made a pull request! Here are some steps to do while waiting for a maintainer to review the pull request:
-1. Check if the filename, file format, and records are valid. If you don't know if it's valid, please read [this part](https://docs.is-a.dev/domain-structure) of the documentation and use a JSON validator/formatter, like [jsonlint](https://jsonlint.com). Make sure that the file is in the `domains` directory and not somewhere else in the repository.
-2. Please make sure that you've filled out the pull request template. It is generally not a good idea to overwrite the pull request template with something else unless you know what you are doing. Make sure to add either a publicly available preview of your website or a screenshot of it.
-3. Please wait patiently. Pull requests may take between a couple hours to 3 days. All of the maintainer team are volunteers and try to review the pull requests in their spare time. If you want a chance of getting your pull request merged faster then send your pull request number **once** in the `#pull-requests` channel in our [Discord server](https://discord.gg/is-a-dev-830872854677422150) and wait patiently.
-4. Please note that mentioning maintainers in pull requests without it being reviewed could lead to you getting marked as "low priority"; this also applies to pinging the maintainers in the Discord server or messaging the maintainers in private to review the pull request.
+1. Check if the checks have failed or passed. You should see the status at the bottom of the pull request or a icon next to the commit ID. You can click on the 3 dots next to the "CI / Tests" check then click "View details", it will show you the logs of the tests.
+2. Check if the filename, file format, and records are valid. If you don't know if it's valid, please read [this part](https://docs.is-a.dev/domain-structure) of the documentation and use a JSON validator/formatter, like [jsonlint](https://jsonlint.com). Make sure that the file is in the `domains` directory and not somewhere else in the repository.
+3. Please make sure that you've filled out the pull request template. It is generally not a good idea to overwrite the pull request template with something else unless you know what you are doing. Make sure to add either a publicly available preview of your website or a screenshot of it.
+4. Please wait patiently. Pull requests may take between a couple hours to 3 days. All of the maintainer team are volunteers and try to review the pull requests in their spare time. If you want a chance of getting your pull request merged faster then send your pull request number **once** in the `#pull-requests` channel in our [Discord server](https://discord.gg/is-a-dev-830872854677422150) and wait patiently.
+5. Please note that mentioning maintainers in pull requests without it being reviewed could lead to you getting marked as "low priority"; this also applies to pinging the maintainers in the Discord server or messaging the maintainers in private to review the pull request.
-Note: Because of the influx of pull requests we are trying to do them all, but this would mean longer wait time. We'll try to get to them when we can. Thanks for the patience.-
\ No newline at end of file
+Note: if you've opened this pull request while there is a high number of other open pull requests, your wait time will be longer than usual. Please be patient!+
\ No newline at end of file
diff --git a/message/merged.md b/message/merged.md
@@ -16,7 +16,7 @@ Just follow the steps below and you can start using your domain!
### Vercel
-You may have to verify the domain so that you can succesfully add the domain to your Vercel website; if you have done that already, the domain should already be connected! If it hasn't, go to the Domain section and click on "Refresh" to see if it works.
+You may have to verify the domain so that you can successfully add the domain to your Vercel website; if you have done that already, the domain should already be connected! If it hasn't, go to the "Domains" section in your project's dashboard and click on "Refresh" to see if it works. If you need to verify the domain with Vercel then please follow our Vercel guide [here](https://docs.is-a.dev/guides/vercel/#creating-the-domain).
### Cloudflare Pages
diff --git a/message/opened.md b/message/opened.md
@@ -2,9 +2,10 @@
You've successfully made a pull request! Here are some steps to do while waiting for a maintainer to review the pull request:
-1. Check if the filename, file format, and records are valid. If you don't know if it's valid, please read [this part](https://docs.is-a.dev/domain-structure) of the documentation and use a JSON validator/formatter, like [jsonlint](https://jsonlint.com). Make sure that the file is in the `domains` directory and not somewhere else in the repository.
-2. Please make sure that you've filled out the pull request template. It is generally not a good idea to overwrite the pull request template with something else unless you know what you are doing. Make sure to add either a publicly available preview of your website or a screenshot of it.
-3. Please wait patiently. Pull requests may take between a couple hours to 3 days. All of the maintainer team are volunteers and try to review the pull requests in their spare time. If you want a chance of getting your pull request merged faster then send your pull request number **once** in the `#pull-requests` channel in our [Discord server](https://discord.gg/is-a-dev-830872854677422150) and wait patiently.
-4. Please note that mentioning maintainers in pull requests without it being reviewed could lead to you getting marked as "low priority"; this also applies to pinging the maintainers in the Discord server or messaging the maintainers in private to review the pull request.
+1. Check if the checks have failed or passed. You should see the status at the bottom of the pull request or a icon next to the commit ID. You can click on the 3 dots next to the "CI / Tests" check then click "View details", it will show you the logs of the tests.
+2. Check if the filename, file format, and records are valid. If you don't know if it's valid, please read [this part](https://docs.is-a.dev/domain-structure) of the documentation and use a JSON validator/formatter, like [jsonlint](https://jsonlint.com). Make sure that the file is in the `domains` directory and not somewhere else in the repository.
+3. Please make sure that you've filled out the pull request template. It is generally not a good idea to overwrite the pull request template with something else unless you know what you are doing. Make sure to add either a publicly available preview of your website or a screenshot of it.
+4. Please wait patiently. Pull requests may take between a couple hours to 3 days. All of the maintainer team are volunteers and try to review the pull requests in their spare time. If you want a chance of getting your pull request merged faster then send your pull request number **once** in the `#pull-requests` channel in our [Discord server](https://discord.gg/is-a-dev-830872854677422150) and wait patiently.
+5. Please note that mentioning maintainers in pull requests without it being reviewed could lead to you getting marked as "low priority"; this also applies to pinging the maintainers in the Discord server or messaging the maintainers in private to review the pull request.
-Note: Because of the influx of pull requests we are trying to do them all, but this would mean longer wait time. We'll try to get to them when we can. Thanks for the patience.-
\ No newline at end of file
+Note: if you've opened this pull request while there is a high number of other open pull requests, your wait time will be longer than usual. Please be patient!+
\ No newline at end of file
diff --git a/package.json b/package.json
@@ -1,7 +1,7 @@
{
"name": "reviewbot",
"private": true,
- "version": "1.0.0",
+ "version": "1.1.0",
"type": "module",
"description": "An app to assist in the review process of is-a-dev",
"author": "iostpa",
