Skip to content

No labels!

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

cherry-pick-approved
cherry-pick-approved
Cherry pick PR approved by release team.
contribution
contribution
Indicates that the PR was contributed by an external member.
dco-signoff: no
dco-signoff: no
Indicates the PR's author has not signed dco.
dco-signoff: yes
dco-signoff: yes
Indicates the PR's author has signed the dco.
dependencies
dependencies
Pull requests that update a dependency file
do-not-merge/hold
do-not-merge/hold
Indicates that a PR should not merge because someone has issued a /hold command.
do-not-merge/release-note-label-needed
do-not-merge/release-note-label-needed
Indicates that a PR should not merge because it's missing one of the release note labels.
do-not-merge/work-in-progress
do-not-merge/work-in-progress
Indicates that a PR should not merge because it is a work in progress.
documentation
documentation
Improvements or additions to documentation
duplicate
duplicate
This issue or pull request already exists
first-time-contributor
first-time-contributor
Indicates that the PR was contributed by an external member and is a first-time contributor.
good first issue
good first issue
Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
help wanted
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
invalid
invalid
This doesn't seem right
javascript
javascript
Pull requests that update Javascript code
lgtm
lgtm
lifecycle/frozen
lifecycle/frozen
lifecycle/rotten
lifecycle/rotten
lifecycle/stale
lifecycle/stale
needs-ok-to-test
needs-ok-to-test
Indicates a PR that requires an org member to verify it is safe to test.
needs-rebase
needs-rebase
Indicates a PR cannot be merged because it has merge conflicts with HEAD.
needs-type
needs-type
ok-to-test
ok-to-test
Indicates a non-member PR verified by an org member that is safe to test.
question
question
Further information is requested
release-note
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
release-note-action-required
release-note-action-required
Denotes a PR that introduces potentially breaking changes that require user action.
release-note-none
release-note-none
Denotes a PR that doesn't merit a release note.
require-LGT1
require-LGT1
Indicates that the PR requires an LGTM.
require-LGT2
require-LGT2
This PR needs to get two LGTMs before merging.