Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

📝 Fix the last remaining okp4 mention in license section #47

Merged
merged 1 commit into from
May 28, 2024

Conversation

ccamel
Copy link
Member

@ccamel ccamel commented May 28, 2024

Self explanatory.

Summary by CodeRabbit

  • Documentation
    • Updated licensing information to reflect that materials now originate from Axone instead of OKP4.

@ccamel ccamel self-assigned this May 28, 2024
Copy link

coderabbitai bot commented May 28, 2024

Walkthrough

The recent update involves a minor but important change in the README.md file, where the origin of materials has been updated from "OKP4" to "Axone". This reflects a shift in the licensing information, ensuring that the correct entity is credited.

Changes

File Change Summary
README.md Updated licensing information from "OKP4" to "Axone".

Poem

In the README, a change took flight,
From OKP4 to Axone, shining bright,
Licensing now reflects the true light,
A small tweak, but oh so right,
Code and words, dancing in the night.


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 full the 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.

@ccamel ccamel marked this pull request as ready for review May 28, 2024 10:19
@ccamel ccamel requested review from amimart and bdeneux May 28, 2024 10:19
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: 0

Outside diff range and nitpick comments (2)
README.md (2)

Line range hint 17-17: Consider updating "Web Site" to "Website" for modern usage consistency.

- [Axone Web Site](https://axone.xyz)
+ [Axone Website](https://axone.xyz)

- [Nemeton Program Web Site](https://nemeton.okp4.network)
+ [Nemeton Program Website](https://nemeton.okp4.network)

Also applies to: 21-21


Line range hint 17-23: Ensure consistent table formatting by adding trailing pipes.

- | URL | Status | History | Response Time | Uptime |
+ | URL | Status | History | Response Time | Uptime |

- | <img alt="" src="https://icons.duckduckgo.com/ip3/axone.xyz.ico" height="13"> [Axone Web Site](https://axone.xyz) | 🟩 Up | [axone-web-site.yml](https://github.com/axone-protocol/status/commits/HEAD/history/axone-web-site.yml) | <details><summary><img alt="Response time graph" src="./graphs/axone-web-site/response-time-week.png" height="20"> 42ms</summary><br><a href="https://status.axone.xyz/history/axone-web-site"><img alt="Response time 42" src="https://img.shields.io/endpoint?url=https%3A%2F%2Fraw.githubusercontent.com%2Faxone-protocol%2Fstatus%2FHEAD%2Fapi%2Faxone-web-site%2Fresponse-time.json"></a><br><a href="https://status.axone.xyz/history/axone-web-site"><img alt="24-hour response time 42" src="https://img.shields.io/endpoint?url=https%3A%2F%2Fraw.githubusercontent.com%2Faxone-protocol%2Fstatus%2FHEAD%2Fapi%2Faxone-web-site%2Fresponse-time-day.json"></a><br><a href="https://status.axone.xyz/history/axone-web-site"><img alt="7-day response time 42" src="https://img.shields.io/endpoint?url=https%3A%2F%2Fraw.githubusercontent.com%2Faxone-protocol%2Fstatus%2FHEAD%2Fapi%2Faxone-web-site%2Fresponse-time-week.json"></a><br><a href="https://status.axone.xyz/history/axone-web-site"><img alt="30-day response time 42" src="https://img.shields.io/endpoint?url=https%3A%2F%2Fraw.githubusercontent.com%2Faxone-protocol%2Fstatus%2FHEAD%2Fapi%2Faxone-web-site%2Fresponse-time-month.json"></a><br><a href="https://status.axone.xyz/history/axone-web-site"><img alt="1-year response time 42" src="https://img.shields.io/endpoint?url=https%3A%2F%2Fraw.githubusercontent.com%2Faxone-protocol%2Fstatus%2FHEAD%2Fapi%2Faxone-web-site%2Fresponse-time-year.json"></a></details> |
Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between 67fe74a and 4b9234f.
Files selected for processing (1)
  • README.md (1 hunks)
Additional Context Used
LanguageTool (2)
README.md (2)

Near line 17: Nowadays, it’s more common to write this as one word.
Context: .../ip3/axone.xyz.ico" height="13"> Axone Web Site | 🟩 Up | [axone-we...
Rule ID: RECOMMENDED_COMPOUNDS


Near line 21: Nowadays, it’s more common to write this as one word.
Context: ...work.ico" height="13"> Nemeton Program Web Site | 🟩 Up ...
Rule ID: RECOMMENDED_COMPOUNDS

Markdownlint (7)
README.md (7)

17: Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe
Table pipe style


18: Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe
Table pipe style


19: Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe
Table pipe style


20: Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe
Table pipe style


21: Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe
Table pipe style


22: Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe
Table pipe style


23: Expected: leading_and_trailing; Actual: leading_only; Missing trailing pipe
Table pipe style

Additional comments not posted (1)
README.md (1)

46-46: Change from "OKP4" to "Axone" in the licensing section is correctly implemented.

Verification successful

No occurrences of "OKP4" were found in the README.md file, confirming that the change to "Axone" is consistent throughout.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify no other mentions of "OKP4" remain in the README.md file.

# Test: Search for "OKP4" in README.md. Expect: No occurrences.
rg --type md 'OKP4' README.md

Length of output: 29

@ccamel ccamel merged commit cb417d5 into main May 28, 2024
4 checks passed
@ccamel ccamel deleted the docs/fix-last-remaining-okp4 branch May 28, 2024 12:03
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