Skip to content

el README manda a la pagina del repositorio original - #8

Open
YuuGR1337 wants to merge 2 commits into
Bitcoindefi:mainfrom
YuuGR1337:fix/issue-7
Open

el README manda a la pagina del repositorio original#8
YuuGR1337 wants to merge 2 commits into
Bitcoindefi:mainfrom
YuuGR1337:fix/issue-7

Conversation

@YuuGR1337

Copy link
Copy Markdown

Fixes #7


Closes Bitcoindefi#7

Signed-off-by: YuuGR1337 <yudhatamvan25@gmail.com>
Comment thread README.md

**Start here:** [Stellar Game Studio](https://jamesbachini.github.io/Stellar-Game-Studio/)

> **Note:** This is a community-maintained fork continuing the work of the original author, [James Bachini](https://github.com/jamesbachini), who sadly passed away. The link above points to his original project page. For the actively maintained version, start with this repository — see the docs in this repo's `docs/` folder. The project remains MIT licensed, with full credit to James for creating Stellar Game Studio.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Quality: Unverified claim that named living person 'passed away'

README.md line 9 asserts that James Bachini "sadly passed away." This is a serious, verifiable real-world claim about a real, named individual (linked to his live GitHub profile). If inaccurate, publishing it in the project README is potentially defamatory and reputationally damaging to the project. This claim cannot be verified from the repository and should not be committed unless confirmed with a reliable source; if the intent is simply to explain the fork, reword to a neutral statement (e.g., "this is a community-maintained fork of James Bachini's original project") that does not make claims about his personal circumstances.

Was this helpful? React with 👍 / 👎

Comment thread README.md

**Start here:** [Stellar Game Studio](https://jamesbachini.github.io/Stellar-Game-Studio/)

> **Note:** This is a community-maintained fork continuing the work of the original author, [James Bachini](https://github.com/jamesbachini), who sadly passed away. The link above points to his original project page. For the actively maintained version, start with this repository — see the docs in this repo's `docs/` folder. The project remains MIT licensed, with full credit to James for creating Stellar Game Studio.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Quality: 'docs/' folder is a built site, not startable documentation

The note tells users to "start with this repository — see the docs in this repo's docs/ folder," but docs/ contains only a generated GitHub Pages build (index.html, 404.html, assets) rather than developer-facing documentation. This may confuse readers looking for onboarding docs. Point users to the actual documentation location, or remove the reference if none exists.

Was this helpful? React with 👍 / 👎

@leocagli

Copy link
Copy Markdown

Thanks for this. The note you added is a good thing to have and I would keep it.

But it does not close #7 yet, because the two links the issue is about are still
pointing at the original repository. On main right now:

README.md:7   **Start here:** [Stellar Game Studio](https://jamesbachini.github.io/Stellar-Game-Studio/)
README.md:27  git clone https://github.com/jamesbachini/Stellar-Game-Studio

The first is the link a new visitor is told to start from, and it does not lead here.
The second means anyone following the quick start clones the upstream repository
instead of this one, so nothing they do lands in this fork.

What would close it

  • Point **Start here:** at this repository
  • Change the git clone line to Bitcoindefi/Stellar-Game-Studio
  • Keep the attribution you added. That part is right and the issue asks for it
    explicitly: this is MIT and crediting the original author is correct.

The remaining jamesbachini.com and YouTube links in the footer are author credit,
not navigation, so those can stay.

Push the change here and I will take another look.

Signed-off-by: YuuGR1337 <yudhatamvan25@gmail.com>
@YuuGR1337

Copy link
Copy Markdown
Author

Thanks for the review — I've updated the PR to address your feedback. Please take another look when you have a moment.

@sonarqubecloud

Copy link
Copy Markdown

@gitar-bot

gitar-bot Bot commented Aug 26, 2026

Copy link
Copy Markdown
Code Review ⚠️ Changes requested 0 resolved / 2 findings

Updates the README repository links to point to the correct destination. However, it introduces an unverified claim about a living person passing away and contains misleading instructions regarding the docs folder.

⚠️ Quality: Unverified claim that named living person 'passed away'

📄 README.md:9

README.md line 9 asserts that James Bachini "sadly passed away." This is a serious, verifiable real-world claim about a real, named individual (linked to his live GitHub profile). If inaccurate, publishing it in the project README is potentially defamatory and reputationally damaging to the project. This claim cannot be verified from the repository and should not be committed unless confirmed with a reliable source; if the intent is simply to explain the fork, reword to a neutral statement (e.g., "this is a community-maintained fork of James Bachini's original project") that does not make claims about his personal circumstances.

💡 Quality: 'docs/' folder is a built site, not startable documentation

📄 README.md:9

The note tells users to "start with this repository — see the docs in this repo's docs/ folder," but docs/ contains only a generated GitHub Pages build (index.html, 404.html, assets) rather than developer-facing documentation. This may confuse readers looking for onboarding docs. Point users to the actual documentation location, or remove the reference if none exists.

🤖 Prompt for agents
Code Review: Updates the README repository links to point to the correct destination. However, it introduces an unverified claim about a living person passing away and contains misleading instructions regarding the docs folder.

1. ⚠️ Quality: Unverified claim that named living person 'passed away'
   Files: README.md:9

   README.md line 9 asserts that James Bachini "sadly passed away." This is a serious, verifiable real-world claim about a real, named individual (linked to his live GitHub profile). If inaccurate, publishing it in the project README is potentially defamatory and reputationally damaging to the project. This claim cannot be verified from the repository and should not be committed unless confirmed with a reliable source; if the intent is simply to explain the fork, reword to a neutral statement (e.g., "this is a community-maintained fork of James Bachini's original project") that does not make claims about his personal circumstances.

2. 💡 Quality: 'docs/' folder is a built site, not startable documentation
   Files: README.md:9

   The note tells users to "start with this repository — see the docs in this repo's `docs/` folder," but docs/ contains only a generated GitHub Pages build (index.html, 404.html, assets) rather than developer-facing documentation. This may confuse readers looking for onboarding docs. Point users to the actual documentation location, or remove the reference if none exists.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Auto-apply Compact
gitar auto-apply:on         
gitar display:verbose         

Important

Your trial ends in 6 days — upgrade now to keep code review, CI analysis, auto-apply, custom automations, and more.

Was this helpful? React with 👍 / 👎 | Gitar

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.

el README manda a la pagina del repositorio original

2 participants