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

Change to Apache License && Update publish.yml #378

Merged
merged 2 commits into from
Apr 17, 2024
Merged

Conversation

sudoskys
Copy link
Member

@sudoskys sudoskys commented Apr 17, 2024

Summary by CodeRabbit

  • Chores
    • Updated the tag pattern for triggering workflows to enhance automation consistency.
    • Transitioned the license from GNU GPL Version 3 to Apache License Version 2.0.

Signed-off-by: Jasmine <[email protected]>
Copy link
Contributor

coderabbitai bot commented Apr 17, 2024

Walkthrough

The recent changes encompass a shift in licensing terms from the GNU General Public License (GPL) Version 3 to the Apache License Version 2.0 for the project. This transition signifies a move towards a different set of permissions, responsibilities, and definitions governing the use, distribution, and modification of the project's codebase.

Changes

File Change Summary
LICENSE Transitioned from GPL Version 3 to Apache License Version 2.0, emphasizing copyright and patent licenses, contributions, and liability.
.github/workflows/publish.yml Altered the tag pattern for workflow trigger from pypi-* to pypi_*.

Recent Review Details

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 9841911 and cb05b6d.
Files selected for processing (1)
  • LICENSE (1 hunks)
Additional comments not posted (1)
LICENSE (1)

1-201: The transition from GNU GPL v3 to Apache License 2.0 has been successfully implemented. The text appears to be correctly formatted and complete, aligning with the standard Apache License 2.0 template.


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.

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 a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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.

Signed-off-by: Jasmine <[email protected]>
@sudoskys sudoskys changed the title Update publish.yml Change to Apache License && Update publish.yml Apr 17, 2024
@sudoskys sudoskys merged commit 6c05fec into main Apr 17, 2024
Copy link
Contributor

@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

.github/workflows/publish.yml Show resolved Hide resolved
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.

1 participant