[WIP] Rename branding from 'GitHubBatches' to 'GitHubUpgrade.com'

[Copilot]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

Open a pull request that merges the branding rename branch into the main branch. Details:

Branch to merge: rename/brand-githubupgrade
Target branch (base_ref): main
Repository: SIMARSINGHRAYAT/GitHubUpgrade.com

Summary of the change:

• Replaced product name and UI text from "GitHubBatches" to "GitHubUpgrade.com" or "GitHubUpgrade" where appropriate.
• Updated the extension manifest name and default_title to "GitHubUpgrade.com".
• Updated the User-Agent header in api/index.js from "GitHubBatches" to "GitHubUpgrade.com".

Files changed (already committed on branch):

• README.md
• CONTRIBUTING.md
• auth.html
• api/index.js
• extension/index.html
• social-actions.html
• extension/manifest.json
• instructions.html
• index.html

PR description to use as body (copy-paste-ready):

Title
Rename branding from "GitHubBatches" to "GitHubUpgrade.com"

Summary
This change updates product branding strings across the codebase from "GitHubBatches" to "GitHubUpgrade.com" / "GitHubUpgrade" where appropriate. The edits are intentionally limited to UI text, metadata, and one User-Agent header used in outgoing API requests. Binary assets and external configuration were not modified in this change.

Branch
rename/brand-githubupgrade

Commit
Rename branding from GitHubBatches to GitHubUpgrade.com
debc10e

Files changed (summary)

• README.md
• CONTRIBUTING.md
• auth.html
• api/index.js (User-Agent header)
• extension/index.html
• social-actions.html
• extension/manifest.json
• instructions.html
• index.html

Why

• Replace the old product name in app UI, docs, and extension to consistently reflect the new brand "GitHubUpgrade.com".
• Ensure client/server requests (User-Agent) reflect new branding.

Risks & notes

• External project references (APP_Commit, deployment URLs, repo names) were left untouched where they appear to be distinct targets; these may require manual review to determine if they should also be renamed.
• Image files (logos/icons) containing the old brand were NOT modified in this commit.
• Repository-level settings (GitHub repository display name, repository rename, Vercel project, DNS) are NOT changed by this PR — they must be updated in the respective hosting/service consoles.

PR checklist (pre-merge)

• Review the changed files (listed above) and confirm wording/formatting are correct.
• Confirm there are no remaining hard-coded occurrences of "GitHubBatches" (run repo grep).
• Verify extension manifest name and default_title are acceptable for published extension (if published).
• Confirm the User-Agent change in api/index.js is acceptable for your telemetry/monitoring.
• Confirm external links/badges (APP_Commit links) should remain or be updated.
• Coordinate DNS / hosting / OAuth redirect updates if you will change the public domain.

Verification steps (QA)

1. Build & run locally

   • npm install && npm run dev (or your standard dev/start procedure)
   • Load the main pages: /index.html, /auth.html, /instructions.html, /extension/index.html, /social-actions.html
   • Verify visible branding text shows "GitHubUpgrade" or "GitHubUpgrade.com" as intended.

2. Auth flow smoke test

   • Click "Sign in via GitHub" (or hit /api/auth/login) and ensure OAuth redirect still works.
   • Confirm cookies and session behavior are unchanged.

3. API behavior

   • Run a dry-run generate call (POST /api/generate with sample payload, pushToRemote=false) and confirm no regressions.
   • Confirm outgoing requests include the User-Agent "GitHubUpgrade.com" if observed in logs.

4. Extension / manifest

   • Verify the extension popup shows the updated title and brand name.
   • If you publish the extension, confirm the new name is allowed by store policies.

5. Social & community interactions

   • On the "Support the project" page, ensure star/follow actions function (/api/social-actions).

Assets & items to replace (post-PR)

• Replace logo files containing the old text: logo.png, favicon.png, social preview images, any screenshots.
• Update any alt text that still mentions the old brand.
• Replace images embedded in README or docs (screenshots, badges with branding).
• Update any SVGs that include text strings with the old brand.

External settings to update (post-merge / manual)

• GitHub repository:
  • Repo display name (if you want name to match brand)
  • Repo description
  • Topics / website link
  • Rename repository if desired (note: renaming affects clones & links)
• Vercel / hosting:
  • Project name and environment variables (APP_BASE_URL, etc.)
  • Update build/deploy settings to reflect new domain if you change it.
• OAuth App settings on GitHub:
  • Redirect URIs (if domain or path changes)
  • Application name visible to users (optional)
• Chrome Web Store / Browser extension listing:
  • Display name, description, screenshots
• DNS / domain:
  • Configure domain GitHubUpgrade.com -> hosting (if applicable)
• CI/CD badges & links:
  • Update any external badges that reference the previous name or repo.

Post-merge tasks

• Run a full repo grep for leftover occurrences of the old brand; fix as needed.
• Replace binary assets and update commit(s).
• Update documentation & release notes announcing the rename.
• Notify any users/contributors about the rename if repository name or URLs change.

Please create the pull request using the branch rename/brand-githubupgrade into main and open it for review. Include the PR body text above and set the PR title to: "Rename branding from "GitHubBatches" to "GitHubUpgrade.com"".

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: it is GitHubUpgrade.com you have written it GitHubBatches, pls change from everywhere

Assistant: Done — I searched the repository for every occurrence of the brand name "GitHubBatches" and prepared concrete file edits to rename the project to "GitHubUpgrade.com". Below are unified diffs for the files I found that need changes. You can copy these patches and apply them locally, or ask me to hand them off to the Copilot coding agent to open a pull request.

What I changed in each patch:

• Replace "GitHubBatches" with "GitHubUpgrade" (keeps .com handling consistent where needed).
• Replace "GitHubBatches.com" with "GitHubUpgrade.com".
• Update the browser User-Agent value that identified as "GitHubBatches" to "GitHubUpgrade.com".
• Update extension manifest name and title strings.

Patches (apply to the repository files shown):

@@
-  *Tired of losing your GitHub streak because you worked on a private repository? Want to retroactively reflect your coding journey? GitHubBatches is the ultimate automation tool for curating your GitHub profile.*
+  *Tired of losing your GitHub streak because you worked on a private repository? Want to retroactively reflect your coding journey? GitHubUpgrade.com is the ultimate automation tool for curating your GitHub profile.*
@@
-## 🌟 Why GitHubBatches?
+## 🌟 Why GitHubUpgrade.com?
@@
-Whether you've been working on private enterprise code, taking a well-deserved break, or simply forgot to push your local commits, **GitHubBatches** lets you sculpt your graph exactly how you want it.
+Whether you've been working on private enterprise code, taking a well-deserved break, or simply forgot to push your local commits, **GitHubUpgrade.com** lets you sculpt your graph exactly how you want it.

@@
-# Contributing to GitHubBatches
+# Contributing to GitHubUpgrade.com
@@
-If this is something you think you can fix, then fork GitHubBatches and create a branch with a descriptive name.
+If this is something you think you can fix, then fork GitHubUpgrade.com and create a branch with a descriptive name.
@@
-Finally, go to GitHub and make a Pull Request!
+Finally, go to GitHub and make a Pull Request!
@@
-At this point, you should switch back to your master branch and make sure it's up to date with GitHubBatches's master branch:
+At this point, you should switch back to your main branch and make sure it's up to date with GitHubUpgrade.com's main branch:
 

-git remote add upstream https://github.com/SIMARSINGHRAYAT/APP_Commit.git
+git remote add upstream https://github.com/SIMARSINGHRAYAT/APP_Commit.git
git checkout main
git pull upstream main

@@
-    <title>Welcome Aboard | GitHubBatches.com</title>
+    <title>Welcome Aboard | GitHubUpgrade.com</title>
@@
-        <p class="auth-copy">Sign in securely with GitHub OAuth. GitHubBatches never asks you to paste or manage a personal access token.</p>
+        <p class="auth-copy">Sign in securely with GitHub OAuth. GitHubUpgrade.com never asks you to paste or manage a personal access token.</p>

@@
   const response = await fetch(url, {
     ...init,
     headers: {
       Accept: 'application/json',
-      'User-Agent': 'GitHubBatches',
+      'User-Agent': 'GitHubUpgrade.com',
       ...(init.headers || {}),
     },
   });

@@
-    <title>Dashboard | GitHubBatches</title>
+    <title>Dashboard | GitHubUpgrade.com</title>
@@
-          <h1 class="brand-name">GitHubBatches</h1>
+          <h1 class="brand-name">GitHubUpgrade</h1>

@@
-    <title>One More Step | GitHubBatches.com</title>
+    <title>One More Step | GitHubUpgrade.com</title>

@@
-  "name": "GitHubBatches",
+  "name": "GitHubUpgrade.com",
@@
-    "default_title": "Open GitHubBatches"
+    "default_title": "Open GitHubUpgrade.com"
   }

@@
-    <title>Instructions | GitHubBatches</title>
+    <title>Instructions | GitHubUpgrade.com</title>

@@
-    <title>GitHubBatches.com</title>
+    <title>GitHubUpgrade.com</title>
@@
-        <h1 id="brand-heading"><span>GitHubBatches</span><em>.com</em></h1>
+        <h1 id="brand-heading"><span>GitHubUpgrade</span><em>.com</em></h1>

Notes and verifications

• I scanned the repo for literal "GitHubBatches" and "GitHubBatches.com" and prepared edits for every file where they appeared.
• I intentionally adjusted replacements to avoid producing "GitHubUpgrade.com.com" (for example, where the UI split brand and ".com" into separate elements I updated the brand text to "GitHubUpgrade" and kept the ".com" element).
• I updated the User-Agent header string in api/index.js so backend requests reflect the new product name.
• I did not change unrelated repository identifiers (for example, APP_Commit references or internal repo configuration) because those appear to be distinct project links and may be intentionally configured.

Want me to…

1. Hand these changes off to the Copilot coding agent to open a pull request with all edits applied.
2. Apply the patches directly in this repository now (I will update the files in-place).
3. Run a wider search-and-replace (include binary/asset files or change additional branding like images/alt text) and prepare a full migration checklist before making changes.

Which option would you like?

User: change it

Assistant: I'm waiting for your confirmation (accept the dialog) to proceed with applying the branding changes—once you approve I'll continue.

User: @copilot Accepted Confirmation: Are you sure?

Assistant: Done — I replaced the product name everywhere you asked and pushed the changes to a branch.

What I did

• Created branch rename/brand-githubupgrade and committed the branding updates.
• Commit: Rename branding from GitHubBatches to GitHubUpgrade.com
  • URL: debc10e
• Files I updated (9):
  • README.md
  • CONTRIBUTING.md
  • auth.html
  • api/index.js (User-Agent header)
  • extension/index.html
  • social-actions.html
  • extension/manifest.json
  • instructions.html
  • index.html

Notes and caveats

• I intentionally left unrelated identifiers and external project references (like APP_Commit) unchanged where they looked like separate project links or deployment targets. If you want those updated too I can sweep them in a follow-up.
• I updated the extension manifest name/title and the app UI strings, but I did not rename repository-level settings (GitHub repo name, repo description, Vercel project name) — those must be changed in GitHub/Vercel settings or via separate tooling.
• If you have image files (logo.png, etc.) that include the old brand in the filename or inside the image, those need manual replacement and I did not alter binary assets.

What's next

• I can open a pull request from rename/brand-githubupgrade into your main branch so the changes can be reviewed and merged.
• I can run a wider sweep (images, alt text, comments, other files like package.json, deploy config) and either prepare those edits or apply them directly.
• I can update repo metadata suggestions (recommended new description, README badges, and application links) and optionally apply those changes.

Want me to…

1. Hand this change off to the coding agent to open a pull request from rename/brand-githubupgrade into the main branch.
2. Run a full repo-wide brand sweep (including images, package.json, site configs, and any remaining strings) and commit the updates on a new branch.
3. Prepare a short PR description and checklist (rename verification steps, assets to replace, external settings to update) so you can review before merging.

Tell me which option (1, 2, or 3) you'd like and I'll proceed.

User: Prepare a short PR description and checklist (rename verification steps, assets to replace, external settings to update) so you can review before merging.

Assistant: Ready — below is a concise, paste-ready PR title + description and a verification checklist you can use when opening the pull request. I also included a short summary of what I changed and where the branch / commit lives.

File: PR_DESCRIPTION.md

name=PR_DESCRIPTION.md

Title
Rename branding from "GitHubBatches" to "GitHubUpgrade.com"

Summary
This change updates product branding strings across the codebase from "GitHubBatches" to "GitHubUpgrade.com" / "GitHubUpgrade" where appropriate. The edits are intentionally limited to UI text, metadata, and one User-Agent header used in outgoing API requests. Binary assets and external configuration were not modified in this change.

Branch
rename/brand-githubupgrade
Commit
Rename branding from GitHubBatches to GitHubUpgrade.com
https://github.com/SIMARSINGHRAYAT/GitHubUpgrade.com/commit/debc10ea463943dc7a6b6c87d91090f42b1df46b

Files changed (summary)
- README.md
- CONTRIBUTING.md
- auth.html
- api/index.js (User-Agent header)
- extension/index.html
- social-actions.html
- extension/manifest.json
- instructions.html
- index.html

Why
- Replace the old product name in app UI, docs, and extension to consistently reflect the new brand "GitHubUpgrade.com".
- Ensure client/server requests (User-Agent) reflect new branding.

Risks & notes
- External project references (APP_Commit, deployment URLs, repo names) were left untouched where they appear to be distinct targets; these may require manual review to determine if they should also be renamed.
- Image files (logos/icons) containing the old brand were NOT modified in this commit.
- Repository-level settings (GitHub repository display name, repository rename, Vercel project, DNS) are NOT changed by this PR — they must be updated in the respective hosting/service consoles.

PR checklist (pre-merge)
- [ ] Review the changed files (listed above) and confirm wording/formatting are correct.
- [ ] Confirm there are no remaining hard-coded occurrences of "GitHubBatches" (run repo grep).
- [ ] Verify extension manifest name and default_title are acceptable for published extension (if published).
- [ ] Confirm the User-Agent change in api/index.js is acceptable for your telemetry/monitoring.
- [ ] Confirm external links/badges (APP_Commit links) should remain or be updated.
- [ ] Coordinate DNS / hosting / OAuth redirect updates if you will change the public domain.

Verification steps (QA)
1. Build & run locally
   - npm install && npm run dev (or your standard dev/start procedure)
   - Load the main pages: /index.html, /auth.html, /instructions.html, /extension/index.html, /social-actions.html
   - Verify visible branding text shows "GitHubUpgrade" or "GitHubUpgrade.com" as intended.

2. Auth flow smoke test
   - Click "Sign in via GitHub" (or hit /api/auth/login) and ensure OAuth redirect still works.
   - Confirm cookies and session behavior are unchanged.

3. API behavior
   - Run a dry-run generate call (POST /api/generate with sample payload, pushToRemote=false) and confirm no regressions.
   - Confirm outgoing requests include the User-Agent "GitHubUpgrade.com" if observed in logs.

4. Extension / manifest
   - Verify the extension popup shows the updated title and brand name.
   - If you publish the extension, confirm the new name is allowed by store policies.

5. Social & community interactions
   - On the "Support the project" page, ensure star/follow actions function (/api/social-actions).

Assets & items to replace (post-PR)
- Replace logo files containing the old text: logo.png, favicon.png, social preview images, any screenshots.
- Update any alt text that still mentions the old brand.
- Replace images embedded in README or docs (screenshots, badges with branding).
- Update any SVGs that include text strings with the old brand.

External settings to update (post-merge / manual)
- GitHub repository:
  - Repo display name (if you want name to match brand)
  - Repo description
  - Topics / website link
  - Rename repository if desired (note: renaming affects clones & links)
- Vercel / hosting:
  - Project name and environment variables (APP_BASE_URL, etc.)
  - Update build/deploy settings to reflect new domain if you change it.
- OAuth App settings on GitHub:
  - Redirect URIs (if domain or path changes)
  - Application name visible to users (optional)
- Chrome Web Store / Browser extension listing:
  - Display name, description, screenshots
- DNS / domain:
  - Configure domain GitHubUpgrade.com -> hosting (if applicable)
- CI/CD badges & links:
  - Update any external badges that reference the previous name or repo.

Post-merge tasks
- Run a full repo grep for leftover occurrences of the old brand; fix as needed.
- Replace binary assets and update commit(s).
- Update documentation & release notes announcing the rename.
- Notify any users/contributors about the rename if repository name or URLs change.

If you'd like, you can copy-paste the above into the PR body when opening the pull request.

Summary / next steps

• I updated the branch rename/brand-githubupgrade and committed the string replacements. The PR description above is ready to paste into a new PR.

Want me to…

1. Hand this change off to the coding agent to open a pull request from rename/brand-githubupgrade into the main branch using the description above.
2. Run a repo-wide search for any remaining occurrences (including binary names and alternate file encodings) and include any additional replacements on a follow-up branch.
3. Create a checklist PR (small follow-up branch) that replaces image assets (logo, favicon, social preview) and updates README screenshots — I will prepare the asset-change commit messages.

Which of these should I do next?

User: Hand this change off to the coding agent to open a pull request from rename/brand-githubupgrade into the main branch using the description above.

Assistant: I'm ready to open the PR from rename/brand-githubupgrade into main — I'm waiting for your confirmation to proceed.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
app-commit	Ready	Preview	Aug 29, 2026 1:36am