Skip to content

Conversation

@Flexusma
Copy link
Contributor

@Flexusma Flexusma commented Sep 14, 2025

Hi,
due to name changes, I've edited the HypeServ name in the docs.

Lmk if you require any further changes :)

Summary by CodeRabbit

  • Documentation

    • Updated branding from HypeSrv to HypeServ across self-hosting guides.
    • Corrected domains and links to hypeserv.com, including Start button targets.
    • Improved grammar (e.g., “updated” → “updates”) and clarified warnings referencing HypeServ Content Manager.
    • Adjusted table formatting, spacing, and alignment for readability; added minor layout spacing.
    • No changes to images or overall structure.
  • Chores

    • Updated site navigation to point to the renamed installation page and correct link target.

@coderabbitai
Copy link

coderabbitai bot commented Sep 14, 2025

Walkthrough

Renames HypeSrv to HypeServ across self-hosting docs and navigation, updates related links (including domain and page targets), fixes a grammar issue in updating instructions, and adjusts table formatting and spacing in the installation index. No code or functional logic changes.

Changes

Cohort / File(s) Summary
Branding and navigation/link updates
docs/self-hosting/installation/hypeserv.md, docs/self-hosting/installation/index.md, docs/self-hosting/updating.md, mkdocs.yml
Rename HypeSrv → HypeServ across headings/text; update domain hypesrv.net → hypeserv.com; change nav/link targets from hypesrv.mdhypeserv.md.
Formatting and spacing tweaks
docs/self-hosting/installation/index.md
Adjust table header separator/alignment, row spacing, Start button braces; add a blank line before the BisectHosting banner.
Grammar correction
docs/self-hosting/updating.md
Fix “perform updated” → “perform updates” in Docker Standalone section.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I thump with glee: HypeServ’s the word,
Links hop true, no letters blurred.
Tables aligned like rows of clover,
Grammar tidied—hop’s not over.
Ears up high, I stamp “Well served!”
From HypeSrv to HypeServ. 🐇✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title "Change HypeServ naming in docs pages" is concise, directly describes the main change (renaming HypeServ across documentation), and targets the affected area (docs pages), so it accurately conveys the PR intent to reviewers scanning history. It avoids unnecessary detail while remaining specific to the changeset.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (4)
docs/self-hosting/installation/hypeserv.md (2)

8-9: Replace hard tabs with spaces in admonition content.
markdownlint MD010 flags hard tabs; indent with spaces to avoid CI/style noise.

Apply this diff:

-	Due to sharing an IP address with other HypeServ users (who may also be hosting a Discord bot),
+    Due to sharing an IP address with other HypeServ users (who may also be hosting a Discord bot),

41-46: Fix OAuth casing/typo.
Use “OAuth” and “OAuth2” (letter O, not zero) for correctness and searchability.

Apply this diff:

-Make sure you enter the `Bot Token` and `Oauth Secret` from the discord developer dashboard in the `Discord Bot Token` and `Discord 0Auth2 Secret` fields in the `Advanced` Section of your Server Dashboard!
+Make sure you enter the `Bot Token` and `OAuth Secret` from the Discord Developer Portal in the `Discord Bot Token` and `Discord OAuth2 Secret` fields in the `Advanced` section of your Server Dashboard!
docs/self-hosting/installation/index.md (1)

12-15: Table updates LGTM; check CSS class naming.
Label and link updated correctly. The CSS class remains .hypesrv; if styling is brand‑specific, consider renaming to .hypeserv and updating styles; if it’s legacy/neutral styling, keeping it is fine.

docs/self-hosting/updating.md (1)

42-47: Branding update LGTM; tweak product name spacing.
Use “Discord Tickets” consistently.

Apply this diff:

-Your HypeServ installation of DiscordTickets (if done via the `Content Manager`) will automatically check for and perform updates on every (re-)start of your server.
+Your HypeServ installation of Discord Tickets (if done via the `Content Manager`) will automatically check for and perform updates on every (re-)start of your server.
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a982719 and 2f4589f.

📒 Files selected for processing (4)
  • docs/self-hosting/installation/hypeserv.md (1 hunks)
  • docs/self-hosting/installation/index.md (1 hunks)
  • docs/self-hosting/updating.md (1 hunks)
  • mkdocs.yml (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/self-hosting/installation/hypeserv.md

8-8: Hard tabs
Column: 1

(MD010, no-hard-tabs)


9-9: Hard tabs
Column: 1

(MD010, no-hard-tabs)

🔇 Additional comments (5)
docs/self-hosting/installation/hypeserv.md (4)

5-5: Brand rename LGTM.
Title updated to “HypeServ” is consistent with the PR objective.


14-14: Verify updated external link.
Confirm https://hypeserv.com/en/discord-bot-hosting?utm_source=discordtickets-docs is correct and stable; otherwise adjust path/UTM.


21-21: Wipe warning branding LGTM.
Clear and accurate; matches the new name.


56-58: Confirm host naming post‑rebrand.
The example URL uses db01.hysrv.eu. If the provider’s DB hostnames changed with the branding, update this; if not, keep but consider a note that legacy hostnames are expected.

mkdocs.yml (1)

122-122: No redirect required — no occurrences of hypesrv.md remain.
mkdocs.yml (line 122) points to self-hosting/installation/hypeserv.md and docs/self-hosting/installation/hypeserv.md exists; adding a redirect is optional for external bookmarks.

@eartharoid eartharoid merged commit 1b1b026 into discord-tickets:main Sep 14, 2025
3 checks passed
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.

2 participants