-
Notifications
You must be signed in to change notification settings - Fork 0
archive oatmeal #67
archive oatmeal #67
Conversation
Signed-off-by: Bacon <[email protected]>
WalkthroughThe project has been archived, and a note has been added to the README.md file redirecting users to a continuation link. This indicates that the active development of the project has ceased, and users should follow the provided link for further updates or new versions. Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Oatmeal/Sinon is back to me for a rewrite so no more need for it to be a 5183-related project.
Thanks for all the fish.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
Outside diff range and nitpick comments (6)
README.md (6)
Line range hint
9-9
: Consider adding a comma for better readability.- ...lcome to use this code for whatever but no you won't get the token unless we screw... + ...lcome to use this code for whatever, but no you won't get the token unless we screw...
Line range hint
11-11
: Ensure headings are surrounded by blank lines for better readability.+ # Download +
Line range hint
14-14
: Consider using a hyphen in "bleeding-edge" when used as a compound adjective.- Download a bleeding edge build from [here](https://github.com/frc5183/Oatmeal/actions/workflows/build-gradle-jar.yml?query=is%3Acompleted). + Download a bleeding-edge build from [here](https://github.com/frc5183/Oatmeal/actions/workflows/build-gradle-jar.yml?query=is%3Acompleted).
Line range hint
17-17
: Ensure headings are surrounded by blank lines for better readability.+ # Configure +
Line range hint
33-33
: Ensure headings are surrounded by blank lines for better readability.+ # Build +
Line range hint
34-36
: Specify the language for code blocks and ensure they are surrounded by blank lines.+ ```gradle gradlew shadowJar
</blockquote></details> </blockquote></details> <details> <summary>Review details</summary> **Configuration used: CodeRabbit UI** **Review profile: CHILL** <details> <summary>Commits</summary> Files that changed from the base of the PR and between ebcd3ff287dea89a0f62bfae6f8e7aec772b2434 and 74a99cf5b6e6def21722245be1f8439d39579edf. </details> <details> <summary>Files selected for processing (1)</summary> * README.md (1 hunks) </details> <details> <summary>Additional context used</summary> <details> <summary>LanguageTool</summary><blockquote> <details> <summary>README.md</summary><blockquote> [typographical] ~9-~9: It seems that a comma is missing. Context: ...lcome to use this code for whatever but no you won't get the token unless we screw... --- [duplication] ~11-~11: Possible typo: you repeated a word Context: ...en unless we screw up, so don't ask. # Download Download a stable build from [here](https://gith... --- [uncategorized] ~14-~14: If this is a compound adjective that modifies the following noun, use a hyphen. Context: .../frc5183/Oatmeal/releases). Download a bleeding edge build from [here](https://github.com/fr... </blockquote></details> </blockquote></details> <details> <summary>Markdownlint</summary><blockquote> <details> <summary>README.md</summary><blockquote> 1-1: Expected: 1; Actual: 0; Below Headings should be surrounded by blank lines --- 6-6: Expected: 1; Actual: 0; Below Headings should be surrounded by blank lines --- 11-11: Expected: 1; Actual: 0; Below Headings should be surrounded by blank lines --- 17-17: Expected: 1; Actual: 0; Below Headings should be surrounded by blank lines --- 18-18: Expected: 1; Actual: 0; Above Headings should be surrounded by blank lines --- 18-18: Expected: 1; Actual: 0; Below Headings should be surrounded by blank lines --- 29-29: Expected: 1; Actual: 0; Below Headings should be surrounded by blank lines --- 33-33: Expected: 1; Actual: 0; Below Headings should be surrounded by blank lines --- 6-6: null Multiple top-level headings in the same document --- 11-11: null Multiple top-level headings in the same document --- 17-17: null Multiple top-level headings in the same document --- 33-33: null Multiple top-level headings in the same document --- 34-34: null Fenced code blocks should be surrounded by blank lines --- 36-36: null Fenced code blocks should be surrounded by blank lines --- 34-34: null Fenced code blocks should have a language specified </blockquote></details> </blockquote></details> </details> <details> <summary>Additional comments not posted (1)</summary><blockquote> <details> <summary>README.md (1)</summary><blockquote> `4-4`: The continuation link is correctly placed and functional. </blockquote></details> </blockquote></details> </details> <!-- This is an auto-generated comment by CodeRabbit for review status -->
@@ -1,3 +1,8 @@ | |||
# ⚠️ ARCHIVED ⚠️ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ensure headings are surrounded by blank lines for better readability.
+
# ⚠️ ARCHIVED ⚠️
+
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.
# ⚠️ ARCHIVED ⚠️ | |
# ⚠️ ARCHIVED ⚠️ | |
@Trip-kun have fun 🫡🫡🫡🫡