Abhiram is wondering about the internal change

[AbhiramTadepalli]

Problem

dyt we need this?

Solution

I've long liked the idea of having to classify smtg as a bug and/or feature, with the internal label

Additional Context

No response

[justinschwerdtfeger]

Well its intended for Documentation, Code Refactor, or dependencies change (such as changin a library or an update)

I feel these 3 types of issues dont fit cleanly under bug or feature request.

[justinschwerdtfeger]

Like if i think we could simplify some similar components without affecting their functionality, would that fall under a bug or a feature?

If i wanted to improve documentation, is that a bug or a feature?

If i wanted to change a library we use or suggest an update bc of EOL or something, is that a bug or a feature?

[AbhiramTadepalli]

hmm fair. If we get rid of the internal label, then this is chill

[justinschwerdtfeger]

What do you think the issue type should be called instead? right now, the label is called "Task"

[AbhiramTadepalli]

I'm talking specifically about this label ^^

[justinschwerdtfeger]

ah okay