Project

General

Profile

Feature #40972

Make priority field more descriptive

Added by Sebastian Wagner 4 months ago. Updated 4 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Core
Target version:
-
Start date:
07/26/2019
Due date:
% Done:

0%

Source:
Development
Tags:
Backport:
Reviewed:
Affected Versions:

Description

The --priority flag accepts a number, but it's not totally clear, which number I should use.

My proposal would be to also accept names, like

--priority baseline
--priority pr-run
--priority pr-run-high
--priority pr-run-urgent
--priority pr-run-low

Where each name corresponds to a specific value

{
    'baseline': 1000
    'pr-run': 100
    'pr-run-high': 90
    'pr-run-urgent': 50
    'pr-run-low': 110
}[priority]

History

#1 Updated by Nathan Cutler 4 months ago

The priority is higher, the lower the number is.

100 is a good starting point for manually triggered runs.

#2 Updated by Sebastian Wagner 4 months ago

  • Description updated (diff)

#3 Updated by Sebastian Wagner 4 months ago

fixed

#4 Updated by Sebastian Wagner 4 months ago

With something like this, we could have a discussion about good priority values

Also available in: Atom PDF