Skip to content

Latest commit

 

History

History
87 lines (57 loc) · 3.93 KB

sync-labels.md

File metadata and controls

87 lines (57 loc) · 3.93 KB

"Sync Labels" workflow

Workflow file: sync-labels.yml

Use github-label-sync to configure the repository's issue/pull request labels according to the universal, shared, and local label configuration files.

Use of consistent labels across repositories makes repository maintenance and searching of issue and pull request trackers easier.

Some label definitions in the configuration file contain a notes field. This provides additional information about the proper usage of the label when this might not be clear from the label name and description. The notes field is purely for documentation purposes and has no effect on the repository labels.

Non-universal labels

Multiple labels data files can be merged to form the list of labels for the repository. The universal labels must be used in all repositories, but some projects will benefit from the addition of other domain-specific labels.

The configuration file structure is documented here: https://github.com/Financial-Times/github-label-sync#label-config-file

Configuration files for labels that are applicable to multiple projects are hosted here. Add the file name to the jobs.download.strategy.matrix.filename[] in the workflow.

The configuration file for labels that only apply to the specific project should be located at .github/label-configuration-files/local.yml

Maximum string lengths

Label sync will fail with a 422: Validation Failed error if a label configuration string exceeds the maximum length.

  • name: 50
  • description: 100
    • Note: description is truncated at ~45 (depending on width) characters in the labeling menu, so make sure the meaning of the label is clear to the maintainer from the visible subset of the description.

Standardized label colors

These colors have good contrast. When possible, follow the conventions established in the universal labels for the general meaning associated the colors.

  • #940404
  • #ff0000
  • #ffa200
  • #ffff00
  • #00ff00
  • #92a600
  • #008000
  • #00ba9e
  • #00ffff
  • #0000ff
  • #800080
  • #d876e3
  • #ff00ff
  • #c0c0c0

Notes

  • Remove the # from the hex color code before adding it to the color field of the labels definition file.
  • Black and white should not be used due to lacking contrast with the GitHub page background colors (light and dark themes).

Readme badge

Markdown badge:

[![Sync Labels status](https://github.com/REPO_OWNER/REPO_NAME/actions/workflows/sync-labels.yml/badge.svg)](https://github.com/REPO_OWNER/REPO_NAME/actions/workflows/sync-labels.yml)

Replace the REPO_OWNER and REPO_NAME placeholders in the URLs with the final repository owner and name (example).

Asciidoc badge:

image:https://github.com/{repository-owner}/{repository-name}/actions/workflows/sync-labels.yml/badge.svg["Sync Labels status", link="https://github.com/{repository-owner}/{repository-name}/actions/workflows/sync-labels.yml"]

Define the {repository-owner} and {repository-name} attributes and use them throughout the readme (example).

Commit message

Add CI workflow to synchronize with shared repository labels

On every push that changes relevant files, and periodically, configure the repository's issue and pull request labels
according to the universal, shared, and local label configuration files.

PR message

On every push that changes relevant files, and periodically, use [github-label-sync](https://github.com/Financial-Times/github-label-sync) to configure the repository's issue/PR labels according to the universal, shared, and local label configuration files.