Unlabeled
blocked
cla: no
cla: yes
comp: angular/cli
comp: angular/pwa
comp: core & compiler
comp: devkit/architect
comp: devkit/benchmark
comp: devkit/build-angular
comp: devkit/build-ng-packagr
comp: devkit/build-optimizer
comp: devkit/build-webpack
comp: devkit/core
comp: devkit/schematics-cli
comp: devkit/schematics
comp: etc/misc
comp: ngtools/webpack
comp: schematics/angular
comp: schematics/schematics
comp: schematics/update
effort1: easy (hours)
effort2: medium (days)
effort3: hard (weeks/months)
flag: can be closed?
freq1: low
Only reported by a handful of users who observe it rarely
freq2: medium
freq3: high
freq4: critical
Happens to many users every day
good first issue
help wanted
hotlist: angular material
hotlist: devRel
hotlist: release-blocker
jira-sync
need: further discussion
On the agenda for team meeting to determine next steps
need: investigation
Requires some digging to determine if action is needed
need: more info
Reporter must clarify the issue
need: repro steps
We cannot reproduce the issue with the information given
PR action: cleanup
PR action: merge
PR author is ready for this to merge
PR action: review
PR state: blocked
PR state: WIP
PR target: lts-only
Contains a fix to a specific LTS branch
PR target: master-only
Contains new features or breaking changes, goes in next minor/major release
PR target: master & patch
Contains no new features or breaking changes, can go in next patch release
PR target: patch-only
Contains a cherry-pick to the patch release, should not go on master branch
priority: 0 (critical)
priority: 1 (urgent)
priority: 2 (required)
priority: 3 (nice to have)
severity1: confusing
severity2: inconvenient
severity3: broken
severity4: memory/performance
severity5: regression
severity6: security
type: bug/fix
type: docs
type: faq
type: feature
type: refactor
type: RFC / discussion / question
workaround1: non-obvious
workaround1: obvious
workaround2: non-obvious
workaround3: complex
workaround4: none
No labels found. Sorry about that.