Skip to content

Change file list default ordering to newest first#1

Merged
alxgsv merged 1 commit into
mainfrom
fix/change-file-list-default-ordering
Apr 9, 2026
Merged

Change file list default ordering to newest first#1
alxgsv merged 1 commit into
mainfrom
fix/change-file-list-default-ordering

Conversation

@alxgsv

@alxgsv alxgsv commented Apr 8, 2026

Copy link
Copy Markdown
Contributor
  • Change file list default --ordering from datetime_uploaded (oldest first) to -datetime_uploaded (newest first) for a more practical default
  • Add test for the default ordering value

Summary by CodeRabbit

  • New Features
    • The file list command now displays results sorted by upload date in descending order by default, showing the most recently uploaded files first.

@coderabbitai

coderabbitai Bot commented Apr 8, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5dc725bd-faa0-45ff-86d4-e9348ee8d409

📥 Commits

Reviewing files that changed from the base of the PR and between 9e9fa02 and 92ac65b.

📒 Files selected for processing (2)
  • internal/cmd/file.go
  • internal/cmd/file_test.go

Walkthrough

Updated the default file list ordering from ascending to descending by datetime_uploaded. The --ordering flag default changed from "datetime_uploaded" to "-datetime_uploaded", and help text was updated to reflect this behavior. A corresponding test validates the new default ordering value.

Changes

Cohort / File(s) Summary
File List Default Ordering
internal/cmd/file.go, internal/cmd/file_test.go
Changed --ordering flag default from "datetime_uploaded" to "-datetime_uploaded" (descending), updated help text documentation, and added test case TestFileList_DefaultOrdering to verify the new default value is applied when no explicit ordering is specified.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Change file list default ordering to newest first' directly and clearly summarizes the main change: updating the default ordering from oldest-first to newest-first behavior.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/change-file-list-default-ordering

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions

github-actions Bot commented Apr 8, 2026

Copy link
Copy Markdown

PR Build Artifacts

Commit Build Time (UTC)
92ac65b Download 2026-04-08 13:03:33 UTC
Available platforms
  • uploadcare-cli_0.1.1-SNAPSHOT-a244925_darwin_amd64.tar.gz
  • uploadcare-cli_0.1.1-SNAPSHOT-a244925_darwin_arm64.tar.gz
  • uploadcare-cli_0.1.1-SNAPSHOT-a244925_linux_amd64.tar.gz
  • uploadcare-cli_0.1.1-SNAPSHOT-a244925_linux_arm64.tar.gz
  • uploadcare-cli_0.1.1-SNAPSHOT-a244925_linux_armv7.tar.gz
  • uploadcare-cli_0.1.1-SNAPSHOT-a244925_windows_amd64.zip
  • uploadcare-cli_0.1.1-SNAPSHOT-a244925_windows_arm64.zip
How to install
  1. Click Download for the build you want
  2. Download uploadcare-cli-binaries zip
  3. Unzip it — you'll find per-platform archives inside
  4. Extract the archive for your platform (e.g. tar xzf uploadcare-cli_*_darwin_arm64.tar.gz)
  5. Run ./uploadcare

@alxgsv alxgsv requested a review from dcherevatenko April 8, 2026 13:04
@alxgsv alxgsv merged commit be835b1 into main Apr 9, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants