[PR #6391] [MERGED] 📜 Redirect the .com domain to .org #55790

Closed
opened 2026-05-01 03:04:43 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/6391
Author: @MikesGlitch
Created: 12/13/2025
Status: Merged
Merged: 12/13/2025
Merged by: @MikesGlitch

Base: masterHead: netlify-docs-redirect-com


📝 Commits (2)

📊 Changes

1 file changed (+4 additions, -0 deletions)

View changed files

📝 packages/docs/static/_redirects (+4 -0)

📄 Description

actualbudget.com currently points to the netlify deployment.

Github Pages only supports one custom domain per repo so we can't point .com and .org to the same github pages.

This change will keep the .com pointed at netlify, but will redirect the user to the .org domain.

A redirect is better for SEO as well, so it's a better approach than serving the same content across different domains.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/actualbudget/actual/pull/6391 **Author:** [@MikesGlitch](https://github.com/MikesGlitch) **Created:** 12/13/2025 **Status:** ✅ Merged **Merged:** 12/13/2025 **Merged by:** [@MikesGlitch](https://github.com/MikesGlitch) **Base:** `master` ← **Head:** `netlify-docs-redirect-com` --- ### 📝 Commits (2) - [`f3d63b6`](https://github.com/actualbudget/actual/commit/f3d63b6148f9adc88d92a1ecb1e5d94e742683d5) redirect the .com domain to .org - [`4f9ab70`](https://github.com/actualbudget/actual/commit/4f9ab70d67f6e8f40a8649d80138572e49059ffc) ok wabbit ### 📊 Changes **1 file changed** (+4 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `packages/docs/static/_redirects` (+4 -0) </details> ### 📄 Description <!-- Thank you for submitting a pull request! Make sure to follow the instructions to write release notes for your PR — it should only take a minute or two: https://github.com/actualbudget/docs#writing-good-release-notes. Try running yarn generate:release-notes *before* pushing your PR for an interactive experience. --> `actualbudget.com` currently points to the netlify deployment. Github Pages only supports one custom domain per repo so we can't point .com and .org to the same github pages. This change will keep the .com pointed at netlify, but will redirect the user to the .org domain. A redirect is better for SEO as well, so it's a better approach than serving the same content across different domains. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-05-01 03:04:43 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#55790