Add Licensing Tooling

[RoseSecurity]

What and Why

• Generate licensing tooling for each file using Hashicorp's copyright utilities

Summary by CodeRabbit

• New Features

  • Introduced a new configuration file for copyright management.
  • Added a new target in the Makefile for generating tooling licensing.
  • New function for pretty-printing markdown content with styles.

• Bug Fixes

  • Enhanced error handling across various components, ensuring consistent logging and reporting.

• Documentation

  • Added copyright notices and license declarations to multiple files to clarify ownership and licensing.

• Chores

  • Updated dependencies in the project to enhance functionality and maintain compatibility.

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

This pull request introduces comprehensive copyright and licensing updates across the project, adding Apache-2.0 license headers to multiple files and introducing new configuration files for copyright management. A new tools/tools.go file enables automatic copyright header generation, and the go.mod file was updated with numerous dependency changes. The modifications are primarily administrative, focusing on standardizing licensing information and tooling without altering core functionality.

Changes

File/Path	Change Summary
.coderabbit.yaml, .github/FUNDING.yml, FUNDING.yml, cmd/*, internal/*, pkg/utils/*, main.go	Added copyright notice and Apache-2.0 license header
.copywrite.hcl	New configuration file for copyright management
.pre-commit-config.yaml	Added local hooks for formatting and documentation
Makefile	Added generate target for tooling licensing
go.mod	Added multiple dependencies, including github.com/hashicorp/copywrite
internal/output.go	New file with PrettyPrint function for markdown rendering
tools/tools.go	New file with copyright header generation directive

Suggested Labels

no-release

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 657ba65 and 7e5cb01.

⛔ Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

📒 Files selected for processing (28)

• .coderabbit.yaml (1 hunks)
• .copywrite.hcl (1 hunks)
• .github/FUNDING.yml (1 hunks)
• .goreleaser.yaml (1 hunks)
• .pre-commit-config.yaml (1 hunks)
• FUNDING.yml (1 hunks)
• Makefile (1 hunks)
• cmd/docs.go (1 hunks)
• cmd/fix.go (1 hunks)
• cmd/list.go (1 hunks)
• cmd/list_models.go (1 hunks)
• cmd/recommend.go (1 hunks)
• cmd/root.go (1 hunks)
• cmd/version.go (1 hunks)
• cmd/version_test.go (1 hunks)
• go.mod (2 hunks)
• internal/analyzer.go (1 hunks)
• internal/dry_run.go (1 hunks)
• internal/llm.go (1 hunks)
• internal/opentofu_schema.go (1 hunks)
• internal/output.go (1 hunks)
• internal/parser.go (1 hunks)
• internal/terraform_schema.go (1 hunks)
• internal/tui/utils/utils.go (1 hunks)
• main.go (1 hunks)
• pkg/utils/list_models.go (1 hunks)
• pkg/utils/logging.go (1 hunks)
• tools/tools.go (1 hunks)

---

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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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 generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary or @auto-summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai or @auto-title anywhere in the PR title to generate the title automatically.

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.