You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CI for our codebase involves multiple workflows. The workflows run concurrently -- however there is still a conceptual order that is natural for thinking about the completion of the whole process. In our case each of these workflows has the same name as the defining file, and the defining file is prefixed with some numerical digits so that the 'conceptual order' is obvious to a developer just looking at the files in the filesystem.
But nothing can be done to control the order in which these checks are presented in the github ui ... Its just a mess of random checks based on execution speed
It would be vastly easier for the reader of the page to digest the results if the checks were shown in a consistent deterministic order.
In my case, alphabetical by workflow and then sequential by the order the job was defined within the workflow would be ideal. I would also be 100% happy to repeat my ordering constraints for the workflows within the workflow files if I could get like a top-level presentation.display_order field for github action workflows (similar to the presentation.order field in vscode's launch.json).
This new field would not be intended to modify the execution order -- the only desire is to modify the order by which the results are ordered (and grouped) in the ui.
ActionsBuild, test, and automate your deployment pipeline with world-class CI/CDProduct Feedback
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Select Topic Area
Product Feedback
Body
CI for our codebase involves multiple workflows. The workflows run concurrently -- however there is still a conceptual order that is natural for thinking about the completion of the whole process. In our case each of these workflows has the same name as the defining file, and the defining file is prefixed with some numerical digits so that the 'conceptual order' is obvious to a developer just looking at the files in the filesystem.
But nothing can be done to control the order in which these checks are presented in the github ui ... Its just a mess of random checks based on execution speed
![image](https://private-user-images.githubusercontent.com/434034/318184369-170ed617-989b-4b73-9139-cbb81e22c7bf.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk5MzAwNDAsIm5iZiI6MTcxOTkyOTc0MCwicGF0aCI6Ii80MzQwMzQvMzE4MTg0MzY5LTE3MGVkNjE3LTk4OWItNGI3My05MTM5LWNiYjgxZTIyYzdiZi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNzAyJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDcwMlQxNDE1NDBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT04ZDYxZDMzYTM1ZjBlNjRmYzNmYzJlMDZhYmIxMTZjOGQ5OWNlZjdlOTQxODc0NDBlYmZmNmI5OWNhNDNjNzYyJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.k1o7qrC6V1yYdM146Um_7gMqz-F1s6i_Ko05U6fYg9w)
It would be vastly easier for the reader of the page to digest the results if the checks were shown in a consistent deterministic order.
In my case, alphabetical by workflow and then sequential by the order the job was defined within the workflow would be ideal. I would also be 100% happy to repeat my ordering constraints for the workflows within the workflow files if I could get like a top-level
presentation.display_order
field for github action workflows (similar to thepresentation.order
field in vscode's launch.json).This new field would not be intended to modify the execution order -- the only desire is to modify the order by which the results are ordered (and grouped) in the ui.
Beta Was this translation helpful? Give feedback.
All reactions