# How do you handle GitHub LFS limits while relying on Actions for CI/CD?

GitHub’s web UI and code navigation feel straightforward for onboarding, and GitHub Actions has been reliable for CI/CD with fast search and pull request diffs. Copilot also helps cut down repetitive coding and documentation, and having pull requests plus a central repo reduces version control chaos and manual deployments. The downsides for me are confusing Git LFS setup and bandwidth limits, plus basic issue tracking and project boards and rising costs for seats and extra Actions minutes at scale. How are you managing LFS-heavy repos and keeping CI/CD costs predictable as your workflows grow?

##### Post Metadata
- Posted at: about 15 hours ago
- Author title: Postdoctoral Researcher, IIT Kanpur | Ph.D. (ECE) | IIT Roorkee | Hardware Security | PUF-based Authentication | Side-Channel Analysis | FPGA Cryptography
- Net upvotes: 1



## Related Product
[GitHub](https://www.g2.com/products/github/reviews)

## Related Category
[Version Control Hosting](https://www.g2.com/categories/version-control-hosting)

## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4