Skip to content

No labels!

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

115 labels

Sort
Sort
Alphabetically
Reverse alphabetically
Most issues
Fewest issues
client:kiota
client:kiota
Focused on core project client kiota
client: metadata
client: metadata
client:OpenAPI.NET.OData
client:OpenAPI.NET.OData
Focused on core project client OpenAPI.NET.OData
client:raptor
client:raptor
Focused on core project client raptor
dependencies
dependencies
Pull requests that update a dependency file
3
dependency:custom
dependency:custom
Issue caused by core project dependency modules or library eg for DevX API, dependency:OData
dependency:graph-explorer
dependency:graph-explorer
Awaiting fix from core dependency project graph explorer
dependency: kiota
dependency: kiota
1
dependency:kiota
dependency:kiota
Awaiting fix from core dependency project modules kiota
dependency: metadata
dependency: metadata
2
dependency: OpenAPI.NET.OData
dependency: OpenAPI.NET.OData
Tasks targeting the OpenAPI.NET.OData library
3
dependency:OpenAPI.NET.OData
dependency:OpenAPI.NET.OData
Awaiting fix from core dependency project modules OpenAPI.NET.OData
dependency: OpenAPI.NET
dependency: OpenAPI.NET
Tasks targetting the OpenAPI.NET library
dependency:raptor
dependency:raptor
Awaiting fix from core dependency project modules raptor
external dependency
external dependency
Default GitHub depandabot package update
for:MS-Q&A
for:MS-Q&A
An issue that's better suited for Microsoft Q&A
for:stackoverflow
for:stackoverflow
An issue that's better suited for stackoverflow.com
github_actions
github_actions
Pull requests that update Github_actions code
good first issue
good first issue
Good for newcomers
goodfirstissue
goodfirstissue
Standard GitHub label used for easy to resolve issues targeting beginner contributors
Needs: Attention 👋
Needs: Attention :wave:
Needs: Author Feedback
Needs: Author Feedback
.NET
.NET
Pull requests that update .net code
1
NICKEL
NICKEL
3
no-recent-activity
no-recent-activity
priority: p0
priority: p0
Blocking issue. Sometimes for p0 bug , an ICM may be filed for the issue to communicate urgency. P0
priority:p0
priority:p0
Blocking issue. Loss of critical functions eg security/privacy violation. Bug SLA<=48hrs
priority: p1
priority: p1
High priority but not blocking. For p1 bug, it causes major but not critical loss of functionality o
priority:p1
priority:p1
High priority/Major issue but not blocking or Big percentage of customers affected. Bug SLA <=7days
priority: p2
priority: p2
Medium. For a p2 bug, they generally have a work-around and only a smaller sub-set of customers is a
1