Skip to content

docs: replace dead X handle link with GitHub org - #864

Open
yzxcj797 wants to merge 1 commit into
altic-dev:mainfrom
yzxcj797:fix/dead-x-link
Open

docs: replace dead X handle link with GitHub org#864
yzxcj797 wants to merge 1 commit into
altic-dev:mainfrom
yzxcj797:fix/dead-x-link

Conversation

@yzxcj797

Copy link
Copy Markdown

The README links to x.com/ALTIC_DEV (badge and text) which returns 404 — the handle appears to have been removed. Updated both occurrences to the GitHub org (github.com/altic-dev), which is live and the natural place for project followers.

@github-actions github-actions Bot added needs PR template Pull request is missing required template content. needs screenshots Pull request needs screenshot or video evidence. labels Aug 15, 2026
@github-actions

Copy link
Copy Markdown

The PR Policy check is blocking this PR because required template information is missing.

Please update the PR description with:

  • Description
  • Type of Change
  • Related Issue or Discussion
  • Testing
  • Screenshots / Video

Screenshots or video are required for UI, UX, settings, onboarding, overlay, menu bar, or visual behavior changes. If this PR has no visual changes, check the no-visual-change box in the template.

If this remains incomplete for 48 hours after opening, the PR may be closed.

@greptile-apps

greptile-apps Bot commented Aug 15, 2026

Copy link
Copy Markdown

Greptile Summary

The PR replaces two dead X-profile destinations in the README with the project's live GitHub organization.

  • Redirects the social badge to the GitHub organization.
  • Redirects the community-section development link to the GitHub organization.
  • Leaves both links labeled and branded as X.

Confidence Score: 4/5

The PR is safe to merge, but the two updated links should be relabeled so their visible GitHub destination is not presented as X.

The destinations are live, but both changed anchors retain X-specific text and branding, producing misleading documentation rather than a runtime defect.

Files Needing Attention: README.md

Fix all with Greploop

Fix All in Codex

Prompt To Fix All With AI
### Issue 1
README.md:6
**GitHub links retain X labels**

Both updated anchors now lead to the GitHub organization, but their visible text, badge branding, and alt text still advertise X and `@ALTIC_DEV`, so readers expecting the project's X account are sent to a differently labeled destination.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Reviews (1): Last reviewed commit: "docs: replace dead X handle link with Gi..." | Re-trigger Greptile

Comment thread README.md
<a href="https://github.com/altic-dev/FluidVoice/stargazers"><img src="https://img.shields.io/github/stars/altic-dev/FluidVoice?style=social" alt="GitHub stars"/></a>
<a href="https://github.com/sponsors/altic-dev"><img src="https://img.shields.io/badge/Sponsor-GitHub%20Sponsors-ea4aaa?logo=githubsponsors&logoColor=white" alt="Sponsor FluidVoice"/></a>
<a href="https://x.com/ALTIC_DEV"><img src="https://img.shields.io/badge/X-%40ALTIC__DEV-black?logo=x&logoColor=white" alt="X @ALTIC_DEV"/></a>
<a href="https://github.com/altic-dev"><img src="https://img.shields.io/badge/X-%40ALTIC__DEV-black?logo=x&logoColor=white" alt="X @ALTIC_DEV"/></a>

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 GitHub links retain X labels

Both updated anchors now lead to the GitHub organization, but their visible text, badge branding, and alt text still advertise X and @ALTIC_DEV, so readers expecting the project's X account are sent to a differently labeled destination.

Prompt To Fix With AI
This is a comment left during a code review.
Path: README.md
Line: 6

Comment:
**GitHub links retain X labels**

Both updated anchors now lead to the GitHub organization, but their visible text, badge branding, and alt text still advertise X and `@ALTIC_DEV`, so readers expecting the project's X account are sent to a differently labeled destination.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Fix in Codex

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dcae91ac9b

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread README.md
Join our Discord: https://discord.gg/VUPHaKSvYV

Follow development on X: [@ALTIC_DEV](https://x.com/ALTIC_DEV)
Follow development on X: [@ALTIC_DEV](https://github.com/altic-dev)

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Relabel these links as GitHub destinations

When readers use either changed link, the visible text and badge still advertise the removed X account (X @ALTIC_DEV), but the link now opens the GitHub organization. This leaves the README presenting a nonexistent social account and makes the destination misleading; update the Community wording and the badge image/alt text to identify GitHub instead.

Useful? React with 👍 / 👎.

@grohith327

Copy link
Copy Markdown
Collaborator

Can you change it to this instead https://x.com/fluidvoiceapp

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

Labels

needs PR template Pull request is missing required template content. needs screenshots Pull request needs screenshot or video evidence.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants