Skip to content

chore(instructions): add data-ownership phrasing convention#7357

Merged
jstirnaman merged 2 commits into
masterfrom
docs/data-ownership-phrasing
Jun 18, 2026
Merged

chore(instructions): add data-ownership phrasing convention#7357
jstirnaman merged 2 commits into
masterfrom
docs/data-ownership-phrasing

Conversation

@jstirnaman

Copy link
Copy Markdown
Contributor

What

Adds a content style guideline to .github/instructions/content.instructions.md (auto-applied to content/**/*.md): use data-ownership framing in import/write/load guidance.

Point the verb at the resource the user owns ("import your data into a database or table"), not at the product ("import data into InfluxDB"). The user owns their data in their own object storage; InfluxDB reads and writes it but doesn't take custody of it.

Why

Surfaced as author feedback while writing the InfluxDB 3.10 bulk-import guide. Capturing it as a durable, checked-in convention so it's applied consistently going forward rather than living in ephemeral notes.

Scope

  • One bullet added to the Style Guidelines section. No rendered-page impact (instructions file), so no preview pages.

@jstirnaman jstirnaman requested a review from a team as a code owner June 17, 2026 03:13
@jstirnaman jstirnaman requested review from sanderson and removed request for a team June 17, 2026 03:13
@github-actions

github-actions Bot commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Vale Style Check Results

Metric Count
Errors 0
Warnings 0
Suggestions 0

Check passed

@jstirnaman jstirnaman merged commit 93223d2 into master Jun 18, 2026
12 checks passed
@jstirnaman jstirnaman deleted the docs/data-ownership-phrasing branch June 18, 2026 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants