Actions
Feature #40972
openMake priority field more descriptive
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