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

feat: LICENSEを追加 #37

Merged
merged 1 commit into from
Jun 17, 2024
Merged

feat: LICENSEを追加 #37

merged 1 commit into from
Jun 17, 2024

Conversation

KeiTa4446
Copy link
Collaborator

@KeiTa4446 KeiTa4446 commented Jun 17, 2024

Close #0

Description(変更内容)

  • LICENSEを追加

...

Manual Testing(手動テスト)

Not required / 不要

Summary by CodeRabbit

  • ドキュメント
    • GNU一般公衆利用許諾契約書(GPL)をバージョン2(1991年6月)に更新しました。

@KeiTa4446 KeiTa4446 requested a review from Kanahiro June 17, 2024 07:25
@KeiTa4446 KeiTa4446 self-assigned this Jun 17, 2024
Copy link

coderabbitai bot commented Jun 17, 2024

Walkthrough

全体の変更は、LICENSE.txtファイルのGNU General Public Licenseを1991年6月のバージョン2に更新することです。この更新は、ソフトウェアのコピー、配布、および修正に関する詳細な条件を提供し、ユーザー全員がソフトウェアを自由に使用できるようにするための特許ライセンスの制限を含む多数の条項を含んでいます。

Changes

ファイル 変更内容
LICENSE.txt GNU General Public Licenseをバージョン2に更新

Poem

ソフトの自由を守るため、

ライセンスを変えたよ、みんなのため。

バージョン2で進めばいい、

コードは今もさらに輝く、自由に。

うさぎも喜ぶ、この更新、

みんなのソフトが自由の限り!


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.

@KeiTa4446 KeiTa4446 changed the title feat: optimize release.yaml by removing unnecessary directory feat: LICENSEを追加 Jun 17, 2024
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: 5

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9abde65 and f38ee27.

Files selected for processing (1)
  • LICENSE.txt (1 hunks)
Additional context used
LanguageTool
LICENSE.txt

[style] ~22-~22: Consider using only “Public” to avoid wordiness. (GENERAL_XX)
Context: ...e referring to freedom, not price. Our General Public Licenses are designed to make sure that...


[typographical] ~46-~46: The conjunction “so that” does not require a comma. (SO_THAT_UNNECESSARY_COMMA)
Context: ... that what they have is not the original, so that any problems introduced by others will ...


[grammar] ~88-~88: It seems that a verb is missing. (MD_DT_JJ)
Context: ...cal act of transferring a copy, and you may at your option offer warranty protectio...


[style] ~122-~122: ‘each and every’ might be wordy. Consider a shorter alternative. (EN_WORDINESS_PREMIUM_EACH_AND_EVERY)
Context: ...extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus,...


[style] ~197-~197: To make your writing clearer, consider a shorter, more direct phrase. (AS_A_CONSEQUENCE_OF)
Context: ...hird parties to this License. 7. If, as a consequence of a court judgment or allegation of paten...


[style] ~202-~202: ‘So as to’ expresses purpose and is used in formal texts. Consider using “to”. (SO_AS_TO)
Context: ...this License. If you cannot distribute so as to satisfy simultaneously your obligations...


[uncategorized] ~203-~203: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ... other pertinent obligations, then as a consequence you may not distribute the Program at a...


[typographical] ~290-~290: Conjunctions like ‘and’ should not follow semicolons. Consider using a comma, or removing the conjunction. (CONJUNCTION_AFTER_SEMICOLON)
Context: ...ctively convey the exclusion of warranty; and each file should have at least the "copyrigh...


[typographical] ~320-~320: Unpaired symbol: ‘'’ seems to be missing (EN_UNPAIRED_QUOTES)
Context: ...pothetical commands show w' and show c' should show the appropriate parts of th...


[typographical] ~322-~322: Unpaired symbol: ‘'’ seems to be missing (EN_UNPAIRED_QUOTES)
Context: ... use may be called something other than show w' and show c'; they could even be mouse-...


[typographical] ~322-~322: Unpaired symbol: ‘'’ seems to be missing (EN_UNPAIRED_QUOTES)
Context: ...omething other than show w' and show c'; they could even be mouse-clicks or men...


[typographical] ~330-~330: Unpaired symbol: ‘'’ seems to be missing (EN_UNPAIRED_QUOTES)
Context: ...t interest in the program `Gnomovision' (which makes passes at compilers) writt...


[uncategorized] ~332-~332: Loose punctuation mark. (UNLIKELY_OPENING_PUNCTUATION)
Context: ... James Hacker. , 1 April 1989 Ty Coon, President of Vi...

Additional comments not posted (2)
LICENSE.txt (2)

22-22: 「General Public Licenses」は「Public Licenses」としても十分です。簡潔さを保つために修正を検討してください。

- Our General Public Licenses
+ Our Public Licenses

Likely invalid or redundant comment.

Tools
LanguageTool

[style] ~22-~22: Consider using only “Public” to avoid wordiness. (GENERAL_XX)
Context: ...e referring to freedom, not price. Our General Public Licenses are designed to make sure that...


88-88: 動詞が不足している可能性があります。「offer warranty protection」の部分に動詞を追加することを検討してください。

- you may at your option offer warranty protection
+ you may at your option offer warranty protection in exchange for a fee

Likely invalid or redundant comment.

Tools
LanguageTool

[grammar] ~88-~88: It seems that a verb is missing. (MD_DT_JJ)
Context: ...cal act of transferring a copy, and you may at your option offer warranty protectio...

Also, for each author's protection and ours, we want to make certain
that everyone understands that there is no warranty for this free
software. If the software is modified by someone else and passed on, we
want its recipients to know that what they have is not the original, so
Copy link

Choose a reason for hiding this comment

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

「so that」の前のカンマは不要です。「so that」自体が接続詞として機能しているため、カンマを削除することをお勧めします。

- original, so that any problems introduced by others will
+ original so that any problems introduced by others will
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
want its recipients to know that what they have is not the original, so
want its recipients to know that what they have is not the original so
Tools
LanguageTool

[typographical] ~46-~46: The conjunction “so that” does not require a comma. (SO_THAT_UNNECESSARY_COMMA)
Context: ... that what they have is not the original, so that any problems introduced by others will ...

conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
Copy link

Choose a reason for hiding this comment

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

「so as to」は「to」に置き換えることができます。より直接的で簡潔な表現にするために修正を検討してください。

- distribute so as to satisfy simultaneously your obligations
+ distribute to satisfy simultaneously your obligations
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
distribute so as to satisfy simultaneously your obligations under this
distribute to satisfy simultaneously your obligations under this
Tools
LanguageTool

[style] ~202-~202: ‘So as to’ expresses purpose and is used in formal texts. Consider using “to”. (SO_AS_TO)
Context: ...this License. If you cannot distribute so as to satisfy simultaneously your obligations...


To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
Copy link

Choose a reason for hiding this comment

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

セミコロンの後の「and」は不要です。セミコロンはすでに文を区切っているため、接続詞は冗長となります。

- warranty; and each file should have at least the "copyright
+ warranty; each file should have at least the "copyright
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
convey the exclusion of warranty; and each file should have at least
convey the exclusion of warranty; each file should have at least
Tools
LanguageTool

[typographical] ~290-~290: Conjunctions like ‘and’ should not follow semicolons. Consider using a comma, or removing the conjunction. (CONJUNCTION_AFTER_SEMICOLON)
Context: ...ctively convey the exclusion of warranty; and each file should have at least the "copyrigh...

You are not responsible for enforcing compliance by third parties to
this License.

7. If, as a consequence of a court judgment or allegation of patent
Copy link

Choose a reason for hiding this comment

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

「as a consequence of」をより簡潔な表現に変更することを検討してください。「due to」などが適切です。

- If, as a consequence of a court judgment or allegation of patent
+ If, due to a court judgment or allegation of patent
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
7. If, as a consequence of a court judgment or allegation of patent
7. If, due to a court judgment or allegation of patent
Tools
LanguageTool

[style] ~197-~197: To make your writing clearer, consider a shorter, more direct phrase. (AS_A_CONSEQUENCE_OF)
Context: ...hird parties to this License. 7. If, as a consequence of a court judgment or allegation of paten...

distribute the same sections as part of a whole which is a work based
on the Program, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote it.
Copy link

Choose a reason for hiding this comment

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

「each and every」は冗長な表現です。「each」または「every」のいずれか一方を使用することを検討してください。

- each and every part regardless of who wrote it.
+ each part regardless of who wrote it.
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
entire whole, and thus to each and every part regardless of who wrote it.
entire whole, and thus to each part regardless of who wrote it.
Tools
LanguageTool

[style] ~122-~122: ‘each and every’ might be wordy. Consider a shorter alternative. (EN_WORDINESS_PREMIUM_EACH_AND_EVERY)
Context: ...extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus,...

@Kanahiro Kanahiro merged commit c2c58e8 into main Jun 17, 2024
3 checks passed
@Kanahiro Kanahiro deleted the feature/add-license branch June 17, 2024 07:37
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