Skip to content
This repository has been archived by the owner on Sep 25, 2024. It is now read-only.

archive oatmeal #67

Merged
merged 1 commit into from
May 31, 2024
Merged

archive oatmeal #67

merged 1 commit into from
May 31, 2024

Conversation

Baconing
Copy link
Member

@Trip-kun have fun 🫡🫡🫡🫡

Signed-off-by: Bacon <[email protected]>
@Baconing Baconing requested a review from Trip-kun May 31, 2024 02:00
Copy link

coderabbitai bot commented May 31, 2024

Walkthrough

The 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

Files Change Summary
README.md Added a note marking the project as archived and redirecting users to a continuation link.

Poem

In the meadow of code, we say goodbye,
To a project archived, reaching for the sky.
Follow the new path, where updates gleam,
Continuation awaits, like a bright new dream.
🐇✨


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?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@Trip-kun Trip-kun left a 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.

@Baconing Baconing merged commit 519f73d into master May 31, 2024
1 check passed
@Baconing Baconing deleted the archive branch May 31, 2024 02:02
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: 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 ⚠️
Copy link

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.

Suggested change
# ⚠️ ARCHIVED ⚠️
# ⚠️ ARCHIVED ⚠️

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants