Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Clarify how CodeRabbit seat licenses work #400

Open
@jmacdotorg

Description

@jmacdotorg

The docs could use a lot more clarity on how seat licenses work—especially, but not limited to, the case of an organization that has only public repositories, or a mix of public and private repositories.

Points to clarify here:

  • What do seat licenses even do?
  • How many should I buy, if I'm buying any?
  • Do seat licenses come into play at all for public repositories? What if my org has a mix of public and private repositories?
  • What CodeRabbit products do seat licenses apply to?
    • Cloud-based CodeRabbit?
    • Self-hosted CodeRabbit?
    • The VSCode extension?
    • Others?

Metadata

Metadata

Assignees

Labels

needs triageA new docs bug that needs to be processed and planned by the docs project owners

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions