Fix the copyright notice in the license file

[chadwhitacre]

Hey @rohitpaulk! 👋 I'm getting ready to submit FSL to SPDX and am reviewing existing adoption as part of that. Thanks for picking up 1.1 already! I noticed a small copy/paste error in the copyright notice (and also added the initial year in the range). 🐭

Checklist:

• I've thoroughly self-reviewed my changes
• I've added tests for my changes, unless they affect admin-only areas (or are otherwise not worth testing)
• I've verified any visual changes using Percy (add a commit with [percy] in the message to trigger)

Summary by CodeRabbit

• Documentation
  • Updated copyright information in the license documentation.

[coderabbitai]

Walkthrough

This update involves a simple yet significant modification to the project's licensing documentation. The copyright information has been revised to reflect the correct and updated range of years, extending from 2021 through 2024, and also transitions the copyright holder from "GitButler Inc" to "CodeCrafters, Inc."

Changes

File	Change Summary
LICENSE.md	Updated copyright from "Copyright 2024 GitButler Inc" to "Copyright 2021-2024 CodeCrafters, Inc."

🎉🐰✨
A hop, a skip, in the code we dip,
From GitButler to Crafters, a swift ownership flip.
Through years it spans, from '21 to '24,
A change so small, yet means much more.
Celebrate we do, with a cheer and a clap,
For every line of code, in this digital map.
🌟📜🎈

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

• X
• Mastodon
• Reddit
• LinkedIn

---

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-tests 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 tests 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 tests.
  • @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.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between ae275b2 and 3190617.

Files selected for processing (1)

• LICENSE.md (1 hunks)

Additional comments: 1

LICENSE.md (1)

• 9-9: The update to the copyright notice is crucial for legal accuracy and aligns with the objectives of this PR. It's important to ensure that such information is correct, especially when preparing for broader legal recognition like SPDX submission.

[rohitpaulk]

Yikes. Thanks for catching this @chadwhitacre!