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

docs: config editors by copilot #1147

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sympatheticmoose
Copy link
Contributor

What this PR does / why we need it:

Same as #1145

Prompt:

@github in the same manner as above, create a tutorial for creating a new Config Editor based on examples in this workspace.

The tutorial should use UI compontents from @grafana/ui to construct the various elements. It should advise users to set defaults where possible, and how to do so.

The tutorial should have the following structure:

Introduction (what is a config editor - this should explain that it is how a data source instance can be configured by a user)
Creating a config editor (this should cover at least copnfiguring a URL and basic authentication and storing sensitive data such as API keys in secureJsonData)
Summary

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

@sympatheticmoose sympatheticmoose added no-changelog Don't include in changelog and version calculations documentation Changes only affect the documentation labels Sep 28, 2024
Copy link

Hello! 👋 This repository uses Auto for releasing packages using PR labels.

✨ This PR can be merged. It will not be considered when calculating future versions of the npm packages and will not appear in the changelogs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Changes only affect the documentation no-changelog Don't include in changelog and version calculations
Projects
Status: 🧑‍💻 In development
Development

Successfully merging this pull request may close these issues.

1 participant