Skip to content

Add internal contributor docs #1308

@tobio

Description

@tobio

These docs should cover:

  • How to handle broken Kibana spec updates once this is automated
  • How to gain access to Copilot if it's not available
  • Best practices for utilising LLM's for provider development, including examples
  • Expectations for a smooth review process
  • How to engage with the core provider developers for TF specific help

There's a line to be trodden here between internal and public documentation. If in doubt, things should be added to the public documentation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions