Skip to content

No labels!

There aren’t any labels for this repository quite yet.

35 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
area: api
area: api
Things to do with metasmoke's V2 API - probably for Art.
1
area: blacklists
area: blacklists
area: data edits
area: data edits
Issues which require someone (usually @Undo1) with higher access to fix records
2
area: data explorer
area: data explorer
AKA the data exploders (any of them - JS or SQL)
area: dependencies
area: dependencies
Pull requests that update a dependency file
5
area: flagging
area: flagging
Issues relating to auto, manual and mod flagging
5
area: infrastructure
area: infrastructure
Servers, software, versions, deployments, all of the Stuff that is teward's purview as sysadmin.
1
area: redis
area: redis
Probably one for thesecretmaster. Things to do with how MS uses redis.
4
area: review
area: review
metasmoke's review system and associated things
2
area: SD integration
area: SD integration
This involves coordination with changes in SD.
2
area: search
area: search
Post search on metasmoke
9
area: ui
area: ui
Anything to do with the user interface, particularly UX concerns
18
hacktoberfest
hacktoberfest
HF issues label. Outside of HF, also consider using type: up-for-grabs.
integration: helios
integration: helios
3
invalid
invalid
HF invalid label to make issues not count towards the 5.
ruby
ruby
Pull requests that update Ruby code
3
status: agreed
status: agreed
Discussions that have been discussed and resolved.
status: by design
status: by design
Bugs that aren't bugs, or FRs that come from a misunderstanding (might be cause for a UI issue)
status: completed
status: completed
Resolved/fixed.
status: declined
status: declined
Bugs/FRs that will not be fixed/implemented for various reasons.
status: deferred
status: deferred
We'll do it later. Maybe. 6-8 months.
1
status: needs investigation
status: needs investigation
This needs more investigation.
2
status: norepro
status: norepro
Issues that can't be reproduced in testing.
1
status: planned
status: planned
We like the idea and might get around to it at some point.
6
status: review
status: review
Issues which require revisiting because they may have become obsolete or changed in some way
1
type: bug
type: bug
Buggy or otherwise incorrect behaviour.
24
type: discussion
type: discussion
Something that requires discussion among the team.
2
type: duplicate
type: duplicate
This has been done before.
type: feature request
type: feature request
Requests for a new feature.
32
type: feedback wanted
type: feedback wanted
Issues that need feedback on them before anything further can be done.
2