Skip to content

Conversation

@adityamaru
Copy link

@adityamaru adityamaru commented Nov 22, 2025

docs: BLA-2526 - Update stickydisk limit from 5 to 10 disks

Summary

Updates the README documentation to reflect the new default limit of 10 sticky disks per GitHub Action job (increased from 5). This is part of BLA-2526, which increases the default stickydisk capacity across the platform.

Changes:

  • Updated README.md line 29 from "up to 5 sticky disks" to "up to 10 sticky disks"

Context:
This documentation change is part of a coordinated 3-PR rollout:

  1. Agent PR (#2553 in fa repo): Removes feature flag logic, sets default to 10 stickydisks
  2. Backend PR (#2861 in web repo): Removes enable_more_stickydisks feature flag from job payloads
  3. This PR: Updates public-facing documentation

Review & Testing Checklist for Human

  • Verify coordination with other PRs: Ensure agent PR (#2553) and backend PR (#2861) are merged/deployed before or simultaneously with this documentation update
  • Check for completeness: Search the README for any other references to "5 disks" or similar that might need updating
  • Consider Docker caching caveat: When Docker pull caching is enabled, customers effectively get 9 stickydisk slots (one reserved for Docker cache). Verify if this nuance should be documented in the README or elsewhere

Notes

BLA-2526: This change updates the documentation to reflect the new default limit
of 10 sticky disks per GitHub Action job (increased from 5).

Changes:
- Updated README.md line 29 from 'up to 5 sticky disks' to 'up to 10 sticky disks'

Note: When Docker pull caching is enabled, it reserves one slot, so customers will
effectively have 9 stickydisk slots available in that configuration.

Co-Authored-By: [email protected] <[email protected]>
@linear
Copy link

linear bot commented Nov 22, 2025

@devin-ai-integration
Copy link

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

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.

1 participant