Skip to content

docs: point wallet links to official repos#10

Open
ManuelSalcedo2770 wants to merge 1 commit into
BitgesellOfficial:masterfrom
ManuelSalcedo2770:docs/official-wallet-links
Open

docs: point wallet links to official repos#10
ManuelSalcedo2770 wants to merge 1 commit into
BitgesellOfficial:masterfrom
ManuelSalcedo2770:docs/official-wallet-links

Conversation

@ManuelSalcedo2770

Copy link
Copy Markdown

Summary

  • Point the wallet package metadata to the official BitgesellOfficial wallet repository for issues and source metadata.
  • Point README jsbgl references to the official BitgesellOfficial/jsbgl repository.
  • Leave dist/desktop links unchanged because those repos are not mirrored under BitgesellOfficial.

Verification

  • npm test
  • npm run build
  • git diff --check
  • confirmed BitgesellOfficial/bitgesell-wallet and BitgesellOfficial/jsbgl exist via GitHub API

Submitted as a small documentation/metadata cleanup for the Bitgesell PR bounty hunt: BitgesellOfficial/bitgesell#39. Payout details can be provided after maintainer review/approval.

@MyTH-zyxeon

Copy link
Copy Markdown

Maintainer triage for the Bitgesell PR bounty queue (#39): this is a small repository-metadata/docs cleanup, not a broad wallet behavior change.

What I verified from the PR diff:

  • README.md updates both jsbgl links from the old bitaps-com/jsbgl repository to BitgesellOfficial/jsbgl.
  • package.json updates the issue tracker and repository metadata from epexa/bitgesell-wallet to BitgesellOfficial/bitgesell-wallet.
  • The desktop/distribution links are intentionally left unchanged, which matches the PR body and avoids inventing official mirrors that may not exist.

Recommended maintainer acceptance checks before merge:

  • Confirm BitgesellOfficial/jsbgl is the canonical upstream users should follow for wallet docs.
  • Confirm npm/package metadata accepts the repository string form used here, or convert it to the explicit object form if this package is intended for registry publication.
  • Run the existing npm test / npm run build checks from the PR body if maintainers want runtime confidence, though this diff is metadata/docs-only.

I did not run the wallet locally in this pass, and I am not making a payout claim from this review note.

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