Skip to content

Conversation

@Bobinstein
Copy link
Contributor

@Bobinstein Bobinstein commented Oct 14, 2025

Summary by CodeRabbit

  • Documentation
    • Standardized headings and anchors for clearer navigation.
    • Updated table of contents with revised link targets and more descriptive section titles across Getting Started, Build from Source, and Upload/Download workflows.
    • Reworded and reformatted lists and examples for readability; replaced HTML anchors with plain headings.
    • Aligned cross-references with the new structure (e.g., password supply, listing entities).
    • Applied minor consistency fixes to prerequisites, commands, and examples.

@coderabbitai
Copy link

coderabbitai bot commented Oct 14, 2025

Walkthrough

The README.md was updated to standardize headings and anchors, revise the table of contents links to match new IDs, convert HTML anchors/lists to plain text formats, and make minor text consistency edits across sections and references.

Changes

Cohort / File(s) Summary
Docs: README heading and anchor normalization
README.md
Renamed anchors; reformatted headings to plain Markdown; updated TOC links to new IDs; converted HTML lists/markers to plain lists; adjusted section titles and references (e.g., NVM, Getting Started, Build from Source, Uploading/Downloading); minor text consistency fixes across prerequisites/commands/examples.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A rabbit hops through docs with glee,
Tidying anchors, neat as can be.
Lists now stroll in markdown lanes,
TOCs align with tidy chains.
With headings crisp and links that sing,
I stamp a paw—spring, spring, spring! 🐇✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title succinctly describes the main change of converting HTML in the README to Markdown and aligns with the primary documentation updates present in the diff, making it clear and specific for readers scanning project history.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch PE-8609-README-update

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (6)
README.md (6)

479-486: Fix shell export: command substitution bug.

$(TMP_ARDRIVE_PW) tries to execute a command. Use variable expansion.

 read -rs TMP_ARDRIVE_PW
-export ARDRIVE_DRIVE_PW=$(TMP_ARDRIVE_PW)
+export ARDRIVE_DRIVE_PW="$TMP_ARDRIVE_PW"
+# optional: avoid leaving it around
+# unset TMP_ARDRIVE_PW
 ardrive <some private command> -w /path/to/wallet.json -P

253-260: Grammar nit: extra “a”.

-To test a with a custom version of the `ardrive-core-js` library on your local system, change the `"ardrive-core-js"` line in `package.json` to the root of your local `ardrive-core-js` repo:
+To test with a custom version of the `ardrive-core-js` library on your local system, change the `"ardrive-core-js"` line in `package.json` to the root of your local `ardrive-core-js` repo:

281-286: NPM install command typo.

Use either npm install -g or npm i -g. Current line mixes both.

-# then using the path generated by yarn from the step above:
-npm install i -g /path/to/package.tgz
+# then using the path generated by yarn from the step above:
+npm install -g /path/to/package.tgz

540-542: Typos: “entitites” → “entities”.

-# List a private drive including the `fileKey` and/or `driveKey` of all listed entitites
+# List a private drive including the `fileKey` and/or `driveKey` of all listed entities
@@
-In the case of private entitites, the `--with-keys` flag will make the command to include the keys in the output.
+In the case of private entities, the `--with-keys` flag will make the command include the keys in the output.

Also applies to: 742-747


1051-1054: Duplicate word: “are are”.

-[Arweave Path Manifests][arweave-manifests] are are special `.json` files
+[Arweave Path Manifests][arweave-manifests] are special `.json` files

1283-1285: Missing ardrive prefix and minor grammar.

-upload-file --metadata-gql-tags "Custom Tag Name" "Custom Value" # ...
+ardrive upload-file --metadata-gql-tags "Custom Tag Name" "Custom Value" # ...
@@
- upload-file --metadata-json ' { "json field": "value", "another fields": false } ' # ...
+ardrive upload-file --metadata-json ' { "json field": "value", "another field": false } ' # ...

Also applies to: 1289-1291

🧹 Nitpick comments (4)
README.md (4)

835-841: Casing consistency: “File”.

Match TOC title casing.

-### Download a Single file (BETA)
+### Download a Single File (BETA)

430-441: Replace remaining HTML anchors with Markdown subheadings.

To fully remove HTML, promote these to subheadings with natural anchors: drive-info, derive-drive-key, derive-file-key, get-share-links, get-total-size, get-file-count, manifest-json.

-The relationship between the drive and its root folder is clearly visible when retrieving the drive's info:<a id='drive-info'></a>
+#### Fetching Drive Info
+The relationship between the drive and its root folder is clearly visible when retrieving the drive's info:
@@
-To derive the drive key again for a drive, perform the following:<a id="derive-drive-key"></a>
+#### Derive a Drive Key
+To derive the drive key again for a drive, perform the following:
@@
-To derive the file key again for a file, perform the following:<a id="derive-file-key"></a>
+#### Derive a File Key
+To derive the file key again for a file, perform the following:
@@
-<a id="get-share-links"></a>
+#### Get Share Links for Files in the Drive
@@
-<a id="get-total-size"></a>
+#### Get Total Size of Files in the Drive
@@
-<a id="get-file-count"></a>
+#### Get Total Count of Files in the Drive
@@
-<a id="manifest-json"></a>
+#### Manifest JSON

Note: Update TOC link texts if desired; anchor slugs will remain unchanged.

Also applies to: 455-461, 462-468, 551-557, 572-579, 579-585, 1092-1111


1190-1193: Use long option for dest file name (avoid alias confusion).

Elsewhere you mention --dest-file-name. Using -d may be confused with drive-id in other commands.

-ardrive upload-file --remote-path "https://url/to/file" --parent-folder-id "9af694f6-4cfc-4eee-88a8-1b02704760c0" -d "example.jpg" -w /path/to/wallet.json
+ardrive upload-file --remote-path "https://url/to/file" --parent-folder-id "9af694f6-4cfc-4eee-88a8-1b02704760c0" --dest-file-name "example.jpg" -w /path/to/wallet.json

If -d is an intended alias here, consider documenting it.


171-175: Audience bullets: capitalization consistency.

Optional: capitalize “NFT” and consider “Sysadmins” or “database admins”.

-- ArDrive power users with advanced workflows and resource efficiency in mind: bulk uploaders, those with larger storage demand, game developers, nft creators, storage/db admins, etc.
+- ArDrive power users with advanced workflows and resource efficiency in mind: bulk uploaders, those with larger storage demand, game developers, NFT creators, storage/db admins, etc.
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0425e04 and 2cf2df9.

📒 Files selected for processing (1)
  • README.md (32 hunks)
🧰 Additional context used
🪛 LanguageTool
README.md

[grammar] ~171-~171: There might be a mistake here.
Context: ...s, nft creators, storage/db admins, etc. - Automation tools - Services - Terminal a...

(QB_NEW_EN)


[grammar] ~172-~172: There might be a mistake here.
Context: ...orage/db admins, etc. - Automation tools - Services - Terminal aficionados - Extant...

(QB_NEW_EN)


[grammar] ~173-~173: There might be a mistake here.
Context: ...mins, etc. - Automation tools - Services - Terminal aficionados - Extant and aspiri...

(QB_NEW_EN)


[grammar] ~174-~174: There might be a mistake here.
Context: ... tools - Services - Terminal aficionados - Extant and aspiring cypherpunks For dee...

(QB_NEW_EN)


[grammar] ~379-~379: There might be a mistake here.
Context: ...y types specified by ArFS are: - Drives - Folders - Files Each instance of these ...

(QB_NEW_EN)


[grammar] ~380-~380: There might be a mistake here.
Context: ...ecified by ArFS are: - Drives - Folders - Files Each instance of these entities h...

(QB_NEW_EN)


[grammar] ~450-~450: There might be a mistake here.
Context: ...Drive ID, User-specified Drive Password) - File Key = functionOf(Randomly Generated...

(QB_NEW_EN)


[grammar] ~475-~475: There might be a mistake here.
Context: ... supplying them: - Environment Variable - STDIN - Secure Prompt #### Supplying Yo...

(QB_NEW_EN)


[grammar] ~476-~476: There might be a mistake here.
Context: ...ng them: - Environment Variable - STDIN - Secure Prompt #### Supplying Your Passw...

(QB_NEW_EN)


[grammar] ~859-~859: There might be a mistake here.
Context: ...d will reconstruct the folder hierarchy on local disk as ArFS folders on the perma...

(QB_NEW_EN)


[grammar] ~1395-~1395: Use a hyphen to join words.
Context: .... NOTE: Your cold wallet won't appear on chain until it has received AR. The wor...

(QB_NEW_EN_HYPHEN)


[grammar] ~1399-~1399: There might be a mistake here.
Context: ...y string if none has ever been sent out) - the base fee for an Arweave transaction ...

(QB_NEW_EN)

🔇 Additional comments (1)
README.md (1)

79-89: Anchors validated: all TOC links resolve. No missing anchors detected.

Comment on lines 1393 to 1398
The best cold wallet storage never exposes your seed phrase and/or private keys to the Internet or a compromised system interface. You can use the ArDrive CLI to facilitate cold storage and transfer of AR.
If you need a new cold AR wallet, generate one from an air-gapped machine capable of running the ArDrive CLI by following the instructions in the [Wallet Operations](#wallet-operations) section. Fund your cold wallet from whatever external sources you'd like. NOTE: Your cold wallet won't appear on chain until it has received AR.
The workflow to send the AR out from your cold wallet requires you to generate a signed transaction with your cold wallet on your air-gapped machine via the ArDrive CLI, and then to transfer the signed transaction (e.g. by a file on a clean thumb drive) to an Internet-connected machine and send the transaction to the network via the ArDrive CLI. You'll need two inputs from the Internet-connected machine:
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Hyphenation: “on-chain”.

-NOTE: Your cold wallet won't appear on chain until it has received AR.
+NOTE: Your cold wallet won't appear on-chain until it has received AR.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
The best cold wallet storage never exposes your seed phrase and/or private keys to the Internet or a compromised system interface. You can use the ArDrive CLI to facilitate cold storage and transfer of AR.
If you need a new cold AR wallet, generate one from an air-gapped machine capable of running the ArDrive CLI by following the instructions in the [Wallet Operations](#wallet-operations) section. Fund your cold wallet from whatever external sources you'd like. NOTE: Your cold wallet won't appear on chain until it has received AR.
The workflow to send the AR out from your cold wallet requires you to generate a signed transaction with your cold wallet on your air-gapped machine via the ArDrive CLI, and then to transfer the signed transaction (e.g. by a file on a clean thumb drive) to an Internet-connected machine and send the transaction to the network via the ArDrive CLI. You'll need two inputs from the Internet-connected machine:
The best cold wallet storage never exposes your seed phrase and/or private keys to the Internet or a compromised system interface. You can use the ArDrive CLI to facilitate cold storage and transfer of AR.
If you need a new cold AR wallet, generate one from an air-gapped machine capable of running the ArDrive CLI by following the instructions in the [Wallet Operations](#wallet-operations) section. Fund your cold wallet from whatever external sources you'd like. NOTE: Your cold wallet won't appear on-chain until it has received AR.
The workflow to send the AR out from your cold wallet requires you to generate a signed transaction with your cold wallet on your air-gapped machine via the ArDrive CLI, and then to transfer the signed transaction (e.g. by a file on a clean thumb drive) to an Internet-connected machine and send the transaction to the network via the ArDrive CLI. You'll need two inputs from the Internet-connected machine:
🧰 Tools
🪛 LanguageTool

[grammar] ~1395-~1395: Use a hyphen to join words.
Context: .... NOTE: Your cold wallet won't appear on chain until it has received AR. The wor...

(QB_NEW_EN_HYPHEN)

🤖 Prompt for AI Agents
In README.md around lines 1393 to 1398, the phrase "on chain" is hyphenated
incorrectly; replace "on chain" with the hyphenated form "on-chain" (e.g.,
change "Your cold wallet won't appear on chain until it has received AR." to
"Your cold wallet won't appear on-chain until it has received AR.") and scan the
surrounding sentences for any other instances of "on chain" to update for
consistent hyphenation.

Comment on lines +1399 to 1401
- the last transaction sent OUT from the cold wallet (or an empty string if none has ever been sent out)
- the base fee for an Arweave transaction (i.e. a zero bye transaction). Note that this value could change if a sufficient amount of time passes between the time you fetch this value, create the transaction, and send the transaction.
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Typo: “zero bye” → “zero byte”.

-- the base fee for an Arweave transaction (i.e. a zero bye transaction). Note that this value could change if a sufficient amount of time passes between the time you fetch this value, create the transaction, and send the transaction.
+- the base fee for an Arweave transaction (i.e. a zero byte transaction). Note that this value could change if a sufficient amount of time passes between the time you fetch this value, create the transaction, and send the transaction.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- the last transaction sent OUT from the cold wallet (or an empty string if none has ever been sent out)
- the base fee for an Arweave transaction (i.e. a zero bye transaction). Note that this value could change if a sufficient amount of time passes between the time you fetch this value, create the transaction, and send the transaction.
- the last transaction sent OUT from the cold wallet (or an empty string if none has ever been sent out)
- the base fee for an Arweave transaction (i.e. a zero byte transaction). Note that this value could change if a sufficient amount of time passes between the time you fetch this value, create the transaction, and send the transaction.
🧰 Tools
🪛 LanguageTool

[grammar] ~1399-~1399: There might be a mistake here.
Context: ...y string if none has ever been sent out) - the base fee for an Arweave transaction ...

(QB_NEW_EN)

🤖 Prompt for AI Agents
In README.md around lines 1399 to 1401 the phrase "zero bye transaction" is a
typo; change "bye" to "byte" so the line reads "the base fee for an Arweave
transaction (i.e. a zero byte transaction)." Update that single word and
preserve the rest of the sentence and punctuation.

@Bobinstein Bobinstein merged commit cdec094 into master Oct 15, 2025
2 checks passed
@Bobinstein Bobinstein deleted the PE-8609-README-update branch October 15, 2025 13:31
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.

3 participants