Skip to content

Labels and when to use them

Rolf Bjarne Kvinge edited this page Sep 10, 2020 · 3 revisions

List of all the labels: https://github.com/xamarin/xamarin-macios/labels

Release notes

In order to make it easier to create release notes, all pull requests must have at least one of these labels:

  • bug: the pull request fixes a bug, and should be shown in the list of fixed bugs in the release notes.
  • enhancement: the pull request is a significant enhancement of some kind, and worth mentioning in the release notes.
  • breaking-change: the pull request is a breaking change that should be mentioned in the release notes.
  • community: the pull request is a community contribution, and should be listed in the release notes as such.
  • note-deprecation: a deprecation worth mentioning in the release notes. Typically there's a specific "Deprecated" section where these pull requests should be.
  • note-infrastructure: use this for infrastructure work that's worth mentioning in the release notes
  • note-mention: the release notes should mention this pull request, but there's no reason to highlight it in any way
  • note-highlight: the release notes should show this pull request prominently
  • not-notes-worthy: don't mention this pull request at all in the release notes
  • regression: the pull request is a bug fix for a regression, and should be shown in the list of fixed bugs in the release notes.

It's possible to use more than one of these labels at the same time (for instance enhancement and note-highlight to make the enhancement highlighted in the release notes).

CI

  • build-package
  • disable-packaged-mono
  • enable-device-build
  • run-*-tests
  • skip-*-tests
  • skip-public-jenkins
  • trigger-device-tests

Clone this wiki locally