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
{{ message }}
This repository was archived by the owner on Sep 30, 2024. It is now read-only.
This is a two-part request that can be solved at once. We currently compute available bulk operations in the backend whenever a user selects (one or more) changesets, these operations aren't ordered.
We could get away with ordering if we revert to displaying the static list of operations on the frontend (which was ordered), however, we disable the unavailable operations so the user can't carry out those actions.
Context 1
Context 2
This is a two-part request that can be solved at once. We currently compute available bulk operations in the backend whenever a user selects (one or more) changesets, these operations aren't ordered.
We could get away with ordering if we revert to displaying the static list of operations on the frontend (which was ordered), however, we disable the unavailable operations so the user can't carry out those actions.