Skip to content

Register ignite-pr-checker.is-a.dev#42677

Open
anton-vinogradov wants to merge 5 commits into
is-a-dev:mainfrom
anton-vinogradov:add-ignite-pr-checker
Open

Register ignite-pr-checker.is-a.dev#42677
anton-vinogradov wants to merge 5 commits into
is-a-dev:mainfrom
anton-vinogradov:add-ignite-pr-checker

Conversation

@anton-vinogradov

Copy link
Copy Markdown

Requirements

  • I agree to the Terms of Service.
  • My file is following the domain structure.
  • My website is reachable and completed.
  • My website is software development related.
  • My website is not for commercial use.
  • I have provided contact information in the owner key.
  • I have provided a preview of my website below.

Website Preview

Live now at https://v888764.hosted-by-vdsina.com (moving to https://ignite-pr-checker.is-a.dev once this merges).

Screenshot attached in a comment below.

Website Purpose

Ignite PR Checker is a free, open-source developer tool for the Apache Ignite project. It shows which tests a pull request actually broke — tests that fail in the PR's TeamCity (ci2) RunAll but are stable on master — filtering out pre-existing and flaky failures, and lets maintainers re-trigger CI suites for a PR. It is non-commercial and fully open source: https://github.com/anton-vinogradov/ignite-pr-checker

@anton-vinogradov anton-vinogradov requested a review from a team as a code owner July 5, 2026 09:42
@is-a-dev-reviewbot

Copy link
Copy Markdown

Hi there! 👋

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 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 of the documentation and use a JSON validator/formatter, like jsonlint. 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 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: 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!

@anton-vinogradov

Copy link
Copy Markdown
Author
image

@anton-vinogradov

Copy link
Copy Markdown
Author

Hi! 👋 A gentle follow-up on this one.

Tests are green and there are no review comments, but the PR seems to have been skipped over — PRs both older (#42671, #42673) and newer (#42681#42690) have been merged since. I suspect it just slipped through the batch.

If the A-record to a bare IP is what needs a closer look: that's intentional — the domain points to my VPS hosting an open-source tool for Apache Ignite contributors (https://github.com/anton-vinogradov/ignite-pr-checker), served over HTTPS (the screenshot above is the live site).

Happy to adjust anything if something's off. Thanks for maintaining this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant