Skip to content

Change dev domain to https://dev.xmoj-script.uk/ - #1062

Merged
boomzero merged 9 commits into
XMOJ-Script-dev:devfrom
boomzero:boomzero/devdomain
Oct 6, 2026
Merged

boomzero merged 9 commits into
XMOJ-Script-dev:devfrom
boomzero:boomzero/devdomain

Conversation

@boomzero

@boomzero boomzero commented Oct 6, 2026 •

Copy link
Copy Markdown
Member

What does this PR aim to accomplish?:

Change dev domain to https://dev.xmoj-script.uk/

Also I want to test the new workflow on fork contribs.

How does this PR accomplish the above?:

Change dev domain to https://dev.xmoj-script.uk/


By submitting this pull request, I confirm the following:

  1. I have read and understood the contributor's guide, as well as this entire template. I understand which branch to base my commits and Pull Requests against.
  2. I have commented on my proposed changes within the code.
  3. I have tested my changes.
  4. I am willing to help maintain this change if there are issues with it later.
  5. It is compatible with the GNU General Public License v3.0
  6. I have squashed any insignificant commits. (git rebase)
  7. I have checked that another pull request for this purpose does not exist.
  8. I have considered and confirmed that this submission will be valuable to others.
  9. I accept that this submission may not be used, and the pull request can be closed at the will of the maintainer.
  10. I give this submission freely and claim no ownership to its content.
  11. I have verified that my changes work correctly in both the new UI and the old/classic UI.

  • I have read the above and my PR is ready for review. Check this box to confirm

Summary by Sourcery

Enhancements:

  • Update debug-mode server routing to use the new dev.xmoj-script.uk domain.

boomzero and others added 9 commits October 6, 2026 10:16
PRs created with GITHUB_TOKEN need a maintainer to approve their
workflow runs, so the auto-merge on the actions/temp version PR never
completes on its own. Create it with the app token like the other
workflows. UpdateVersion still skips it because the actor ends in [bot].

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E5dr7XTsCeoamqLSiT9rLp
(cherry picked from commit ce63eaf)
(workflow part of cherry picked commit f117fe9)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E5dr7XTsCeoamqLSiT9rLp
- Remove the dev -> extern-contrib sync and the merge.yml job that
  could never run (its only job required ref extern-contrib).
- UpdateVersion: pass the PR title through env instead of pasting it
  into the shell command.
- Prerelease: skip when a release for the current version exists, so
  a merge without a version bump cannot overwrite a published release.
- Qodana: skip fork PRs, which do not receive QODANA_TOKEN.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E5dr7XTsCeoamqLSiT9rLp
(cherry picked from commit eab4141)
Fork PRs get no secrets and the bot cannot push to forks, so their
version cannot be bumped before merge. On a push to dev that touches
XMOJ.user.js, look up the PR whose merge commit it is; if it came from a
fork, run UpdateVersion in fork-merged mode: bump on actions/version-<PR>
from dev and open an auto-merging PR as the GitHub App. Runs only on the
trusted push, never on fork events, and never checks out fork code.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E5dr7XTsCeoamqLSiT9rLp
(cherry picked from commit 581153a)
- UpdateVersionFork processes every merged fork PR to dev that has no
  Update.json entry, oldest first, each from the latest dev. A run
  dropped by the concurrency group loses nothing: the next run picks
  its PR up.
- fork-merged mode reuses an open version PR on a rerun and waits for
  it to merge, so the next bump starts from a dev with this version.
- Prerelease only skips when the version is already a stable release;
  an existing prerelease of the same version is still refreshed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E5dr7XTsCeoamqLSiT9rLp
(cherry picked from commit 461e194)
Qodana is no longer used and the workflow is disabled on GitHub; this
also drops the fork guard added to it earlier in this PR.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E5dr7XTsCeoamqLSiT9rLp
(cherry picked from commit 0f68da7)
Stable release 4.0.0: merge dev into master
Signed-off-by: Zhu Chenrui <Thomas_rainbowfish@icloud.com>
@sourcery-ai

sourcery-ai Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

Sorry @boomzero, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 3 days and 4 hours by commenting @sourcery-ai review. Upgrade to get a review now.

@sourcery-ai

sourcery-ai Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the userscript’s debug-mode server endpoint from the GitHub Pages domain to https://dev.xmoj-script.uk/, while leaving the production endpoint unchanged. Reviewers should verify debug and non-debug routing, including both new and classic UI flows.

Flow diagram for debug-mode server routing

flowchart TD
    A[Userscript starts] --> B{DebugMode enabled?}
    B -->|Yes| C[ServerURL = https://dev.xmoj-script.uk/]
    B -->|No| D[ServerURL = https://www.xmoj-script.uk/]
    C --> E[Continue UI request flow]
    D --> E
Loading

File-Level Changes

Change Details Files
Point debug-mode requests to the new development domain.
  • Replace the debug server URL with https://dev.xmoj-script.uk/.
  • Preserve production routing to https://www.xmoj-script.uk when debug mode is disabled.
XMOJ.user.js

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@boomzero
boomzero merged commit e2f511c into XMOJ-Script-dev:dev Oct 6, 2026
11 of 12 checks passed
@boomzero
boomzero deleted the boomzero/devdomain branch October 6, 2026 11:16
hendragon-bot Bot added a commit that referenced this pull request Oct 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant