remove reverse: true in listBulkOperations#6813
Merged
jordanverasamy merged 1 commit intomainfrom Feb 3, 2026
Merged
Conversation
jordanverasamy
requested review from
ericlee878,
gonzaloriestra and
nickwesselman
jordanverasamy
changed the title
reverse: true to reverse: false in listBulkOperationsreverse: true in listBulkOperations
ericlee878
approved these changes
Feb 2, 2026
Contributor
ericlee878
left a comment
ericlee878
left a comment
There was a problem hiding this comment.
🎩 successfully! LGTM!!
jordanverasamy
force-pushed
the
jtv/reverse-bulk-status-list-ordering
branch
from
3d0acef to
a7e47aa
Compare
amcaplan
approved these changes
Feb 3, 2026
Contributor
|
We detected some changes at Caution DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release. |
Contributor
Coverage report
Show new covered files 🐣
Show files with reduced coverage 🔻
Test suite run success3715 tests passing in 1438 suites. Report generated by 🧪jest coverage report action from a7e47aa |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
WHY are these changes introduced?
This was actually the intended sort order all along. See the [brief], where we show newest-first sorting: (https://docs.google.com/document/d/157CvTbzxv5RDkAJCCeZMcWEPrsGLEdkFc8Hd48fUSM8/edit?usp=sharing):
I messed this up when initially implementing -- I'd assumed the default sort would be oldest first, so we'd need to reverse it. Turns out the default sort is newest first, so we don't! (We didn't realize the issue before because without the auth fixes, operations would stop being visible to this command fairly quickly.)
WHAT is this pull request doing?
Let's just... not reverse the sort anymore!
How to test your changes?
Run
app bulk statusnow and verify that newest are at the top: