Skip to content

Commit d3ea8ba

Browse files
committed
chore: Add issue template for chore tasks
1 parent a29fbae commit d3ea8ba

1 file changed

Lines changed: 33 additions & 0 deletions

File tree

.github/ISSUE_TEMPLATE/chore.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
name: Chore
3+
about: Track maintenance work for plotly.js (dependency bumps, build/CI, internal refactors, docs)
4+
title: "[CHORE]: "
5+
labels: chore
6+
7+
---
8+
<!--
9+
Instructions (remove this section before submitting issue)
10+
11+
Thanks for your interest in plotly.js!
12+
13+
- Use this template for maintenance work that does not change end-user behavior: dependency updates, build pipeline changes, CI/CD adjustments, internal refactors, lint/format/typing cleanup, or documentation updates.
14+
- For user-facing bugs use the **Bug report** template, and for new functionality use the **Feature request** template.
15+
- Before opening a new chore, please search for existing and closed issues to avoid duplicates.
16+
- Comments should add content to the discussion. Approbation comments such as *+1* will be deleted by the maintainers — use [GitHub reactions](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments) instead.
17+
-->
18+
19+
### Description
20+
21+
<!-- Add a clear description of the update that should be made. -->
22+
23+
### Why should this change be made?
24+
25+
<!-- Provide an argument for why this update should be made. Please consider creating a PR and making the update yourself. Help is always appreciated. -->
26+
27+
### Scope
28+
29+
<!-- Provide specifics on the changes that need to be made. -->
30+
31+
### Notes
32+
33+
<!-- Add info here that doesn't fit in the other sections. -->

0 commit comments

Comments
 (0)