Abhiram is wondering about the internal change
Open
@justinschwerdtfeger is already working on this.
Since Aug 5, 2026.
Assessment
This issue has not been assessed yet.
Description
Type: Internal
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
- Dominant language
- CSS
- Stars
- 0
- Forks
- 0
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from UTDNebula/engineeringSandbox
-
GitHub Action to automatically remove PRs for violating ai policyPossibly taken @Isoscelestial claimed this 32 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
testOpen
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
testOpen
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
Abhiram loves the Feature Request template tooMay be free again @justinschwerdtfeger claimed this 68 days ago, and no pull request is open. Open
UTDNebula/engineeringSandbox#7 · 1 comment · 1 assignee ·
-
Abhiram likes this bug templateMay be free again @justinschwerdtfeger claimed this 68 days ago, and no pull request is open. OpenHelp Wanted
UTDNebula/engineeringSandbox#4 · 1 comment · 1 assignee ·