Merged
Conversation
WalkthroughThis pull request updates Discord invite URLs across multiple documentation files and site components from the old invite code (DE9dtFXjZb) to a new short link (discord.gg/52Y8A7pVxu). Changes span navigation configurations, template partials, and markdown documentation pages. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
pdaoust
force-pushed
the
chore/update-discord-invite-link
branch
from
94abe53 to
66b2bb2
Compare
|
✔️ 66b2bb2 - Conventional commits check succeeded. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In `@src/pages/resources/upgrade/upgrade-holochain-0.2.md`:
- Line 294: Replace the three occurrences of the lowercase "Github" label with
the official "GitHub" spelling in the markdown; search for the string "Github
issue" (the link text pointing to
https://github.com/holochain/holochain/issues/new/choose) and update each
instance to "GitHub" so all link texts read "GitHub issue" (also update any
other "Github" link text in the same file to "GitHub").
In `@src/pages/resources/upgrade/upgrade-holochain-0.3.md`:
- Line 218: Replace the incorrect "Github issue" mentions with the proper
"GitHub issue" capitalization throughout the document: search for the exact
string "Github issue" (appearing in the sentence that links to
https://github.com/holochain/holochain/issues/new/choose) and update all
occurrences to "GitHub issue" so the link text reads correctly in the
upgrade-holochain-0.3.md content.
| The specific changelog entry for this change can be found [here](https://github.com/holochain/holochain/blob/develop-0.2/CHANGELOG.md#holo_hash-020). | ||
|
|
||
| If you have trouble resolving the build issues or the changelog doesn't give you enough information about what has changed, then please reach out on [Discord](https://discord.com/invite/DE9dtFXjZb) or open a [Github issue](https://github.com/holochain/holochain/issues/new/choose). | ||
| If you have trouble resolving the build issues or the changelog doesn't give you enough information about what has changed, then please reach out on [Discord](https://discord.gg/52Y8A7pVxu) or open a [Github issue](https://github.com/holochain/holochain/issues/new/choose). |
There was a problem hiding this comment.
Nit: "Github" should be capitalized as "GitHub".
The official spelling uses a capital "H". This appears on all three changed lines (Lines 294, 298, and 314).
Proposed fix
-If you have trouble resolving the build issues or the changelog doesn't give you enough information about what has changed, then please reach out on [Discord](https://discord.gg/52Y8A7pVxu) or open a [Github issue](https://github.com/holochain/holochain/issues/new/choose).
+If you have trouble resolving the build issues or the changelog doesn't give you enough information about what has changed, then please reach out on [Discord](https://discord.gg/52Y8A7pVxu) or open a [GitHub issue](https://github.com/holochain/holochain/issues/new/choose).-If you depend on other Holochain crates, then you will need to find compatible versions to update to. You can check available versions on `crates.io` by searching for them by name. You can also check the [Holochain changelog](https://github.com/holochain/holochain/blob/develop-0.2/CHANGELOG.md) to see what versions have been released together. Note that we don't release crates unless they have changes, so if you don't see the crate you're looking for in a release, then please check the previous releases for the last time we released it. If you get stuck or have build issues, then please reach out on [Discord](https://discord.gg/52Y8A7pVxu) or open a [Github issue](https://github.com/holochain/holochain/issues/new/choose).
+If you depend on other Holochain crates, then you will need to find compatible versions to update to. You can check available versions on `crates.io` by searching for them by name. You can also check the [Holochain changelog](https://github.com/holochain/holochain/blob/develop-0.2/CHANGELOG.md) to see what versions have been released together. Note that we don't release crates unless they have changes, so if you don't see the crate you're looking for in a release, then please check the previous releases for the last time we released it. If you get stuck or have build issues, then please reach out on [Discord](https://discord.gg/52Y8A7pVxu) or open a [GitHub issue](https://github.com/holochain/holochain/issues/new/choose).-That should be everything; you can now develop against Holochain 0.2! Good luck, and if you need help then please do get in touch on [Discord](https://discord.gg/52Y8A7pVxu) or open a [Github issue](https://github.com/holochain/holochain/issues/new/choose).
+That should be everything; you can now develop against Holochain 0.2! Good luck, and if you need help then please do get in touch on [Discord](https://discord.gg/52Y8A7pVxu) or open a [GitHub issue](https://github.com/holochain/holochain/issues/new/choose).Also applies to: 298-298, 314-314
🧰 Tools
🪛 LanguageTool
[style] ~294-~294: Consider using a different verb to strengthen your wording.
Context: ...e build issues or the changelog doesn't give you enough information about what has c...
(GIVE_INFORMATION)
[uncategorized] ~294-~294: The official name of this software platform is spelled with a capital “H”.
Context: ...tps://discord.gg/52Y8A7pVxu) or open a [Github issue](https://github.com/holochain/hol...
(GITHUB)
🤖 Prompt for AI Agents
In `@src/pages/resources/upgrade/upgrade-holochain-0.2.md` at line 294, Replace
the three occurrences of the lowercase "Github" label with the official "GitHub"
spelling in the markdown; search for the string "Github issue" (the link text
pointing to https://github.com/holochain/holochain/issues/new/choose) and update
each instance to "GitHub" so all link texts read "GitHub issue" (also update any
other "Github" link text in the same file to "GitHub").
| You are likely to run into API changes in the HDK and HDI at this point. You can check the [Holochain changelog](https://github.com/holochain/holochain/blob/develop-0.3/CHANGELOG.md) to see what has changed. In some cases there will be guidance for what you need to change. | ||
|
|
||
| If you have trouble resolving the build issues or the changelog doesn't give you enough information about what has changed, then please reach out on [Discord](https://discord.com/invite/DE9dtFXjZb) or open a [Github issue](https://github.com/holochain/holochain/issues/new/choose). | ||
| If you have trouble resolving the build issues or the changelog doesn't give you enough information about what has changed, then please reach out on [Discord](https://discord.gg/52Y8A7pVxu) or open a [Github issue](https://github.com/holochain/holochain/issues/new/choose). |
There was a problem hiding this comment.
Nit: Same "Github" → "GitHub" capitalization issue as in the 0.2 upgrade guide.
Lines 218, 290, and 309 all use "Github issue" — should be "GitHub issue".
Proposed fix
-If you have trouble resolving the build issues or the changelog doesn't give you enough information about what has changed, then please reach out on [Discord](https://discord.gg/52Y8A7pVxu) or open a [Github issue](https://github.com/holochain/holochain/issues/new/choose).
+If you have trouble resolving the build issues or the changelog doesn't give you enough information about what has changed, then please reach out on [Discord](https://discord.gg/52Y8A7pVxu) or open a [GitHub issue](https://github.com/holochain/holochain/issues/new/choose).-If you get stuck or have build issues, then please reach out on [Discord](https://discord.gg/52Y8A7pVxu) or open a [Github issue](https://github.com/holochain/holochain/issues/new/choose).
+If you get stuck or have build issues, then please reach out on [Discord](https://discord.gg/52Y8A7pVxu) or open a [GitHub issue](https://github.com/holochain/holochain/issues/new/choose).-That should be everything --- you can now develop against Holochain 0.3! Good luck, and once again, if you need help then please do get in touch on [Discord](https://discord.gg/52Y8A7pVxu) or open a [Github issue](https://github.com/holochain/holochain/issues/new/choose).
+That should be everything --- you can now develop against Holochain 0.3! Good luck, and once again, if you need help then please do get in touch on [Discord](https://discord.gg/52Y8A7pVxu) or open a [GitHub issue](https://github.com/holochain/holochain/issues/new/choose).Also applies to: 290-290, 309-309
🧰 Tools
🪛 LanguageTool
[style] ~218-~218: Consider using a different verb to strengthen your wording.
Context: ...e build issues or the changelog doesn't give you enough information about what has c...
(GIVE_INFORMATION)
[uncategorized] ~218-~218: The official name of this software platform is spelled with a capital “H”.
Context: ...tps://discord.gg/52Y8A7pVxu) or open a [Github issue](https://github.com/holochain/hol...
(GITHUB)
🤖 Prompt for AI Agents
In `@src/pages/resources/upgrade/upgrade-holochain-0.3.md` at line 218, Replace
the incorrect "Github issue" mentions with the proper "GitHub issue"
capitalization throughout the document: search for the exact string "Github
issue" (appearing in the sentence that links to
https://github.com/holochain/holochain/issues/new/choose) and update all
occurrences to "GitHub issue" so the link text reads correctly in the
upgrade-holochain-0.3.md content.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary by CodeRabbit
Chores
Documentation