Project

General

Profile

Actions
Copy link

Feature #40972

open

Make priority field more descriptive

Added by Sebastian Wagner over 4 years ago. Updated over 4 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Core
% 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]
Actions
Copy link
 #1

Updated by Nathan Cutler over 4 years ago

The priority is higher, the lower the number is.

100 is a good starting point for manually triggered runs.

Actions
Copy link
 #2

Updated by Sebastian Wagner over 4 years ago

  • Description updated (diff)
Actions
Copy link
 #3

Updated by Sebastian Wagner over 4 years ago

fixed

Actions
Copy link
 #4

Updated by Sebastian Wagner over 4 years ago

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

Actions
Copy link

Also available in: Atom PDF