Github labeling strategy

Priority

• p0 : Utmost priority, do first, requires immediate action
• p1 : High priority goals
• p2 : Important but less time-sensitive tasks
• backlog : Issues we want to keep open, but are helpful to do when others are addressed
• MQ : Issues we want to accomplish during our MQ time

Topic

• autorest : Specific for autorest generations from swagger. Default assumption for this repo is TSP
• bug : This issue requires a change to an existing behavior in the product in order to be resolved
• Community Contribution : Community members are working on the issue
• Customer-reported : Issues that are reported by external users. Responding to these issues is high priority, fixing them is usually high priority
• dependencies : Issues / PRs for updating dependency files
• discussion : An area of design currently under discussion and open to team and community feedback
• docs/samples : Issues relating to any documentation or samples we have. Can be generated or handwritten
• engsys : Related to eng sys of this repo
• Feature-gap : Tsp features that we need to support in our generator
• Feature-request : Request to add a new feature to our generator
• lint/typing : Issues dealing with the generated code's pylint or mypy
• mgmt : Issues related to mgmt generation
• models : Issues related to generated models
• Need-design : The issue requires design and approval as well to merge
• packaging : Related to the packaging of the generated code
• question : Question from a customer. Should be addressed with high priority but might not necesitate a code change
• rearchitecture : Relating to changes in our codebase's structure
• serialization : Serialization and deserialization to and from the service
• tcgc : Work related to tcgc integration
• tests : Related to tests we want to add to our repo
• unbranding : Related to efforts to generate non-Azure SDKs
• versioning : Related to multiapi / package versioning of our generated SDKs