Find out why your Linux disk is full. Spots deleted files still held open, Docker, journald, old kernels, logs and caches, and prints the command that frees each one. Never deletes anything.

Is amlaban65/whyfull beginner-friendly?

In the last 30 days, amlaban65/whyfull merged 10 of 14 pull requests from outside contributors, and its maintainers usually reply within 1 day. 3 beginner-friendly issues are open now.

Stars
3
Forks
4
Open beginner issues
3
Indexed issues
16
Avg merge
4h 49m
Merged PRs (30d)
10
Dominant language
Python
License
MIT
Last GitHub push
Nov 2, 2026
Latest indexed
Nov 3, 2026
Contributing guide
Contributing guide
Code of conduct
No code of conduct
Beginner labels
help wanted good first issue

How to contribute to amlaban65/whyfull

  1. Read the contributing guide first: it says how the maintainers want changes proposed, tested and reviewed.
  2. Your contributions will be published under the project's MIT license.
  3. Pick one of the 3 open beginner-friendly issues below and comment that you want to work on it before you start.

Issues somebody may already be working on are listed last. List everything by date

  • Website guide: find large files and directories on Linux
    Open
    documentation good first issue help wanted

    Difficulty 1/5 1-3 hours Newbie friendliness 84/100

    amlaban65/whyfull#32 ·

    Maintainers usually reply within 1 day

  • Add ccache, sccache, Bazel, Playwright and JetBrains caches to user-caches
    Open
    enhancement good first issue help wanted

    Difficulty 2/5 1-3 hours Newbie friendliness 82/100

    amlaban65/whyfull#30 ·

    Maintainers usually reply within 1 day

  • New check: space held by btrfs and ZFS snapshots
    Open
    help wanted new check

    Difficulty 4/5 3-5 days Newbie friendliness 42/100

    amlaban65/whyfull#29 ·

    Maintainers usually reply within 1 day

  • New check: CI runner work directories (GitLab Runner and GitHub Actions self-hosted runners)
    Open
    good first issue help wanted new check

    Difficulty 3/5 Half a day Newbie friendliness 68/100

    amlaban65/whyfull#28 ·

    Maintainers usually reply within 1 day

  • New check: Elasticsearch and OpenSearch data near the flood-stage watermark
    Open
    good first issue help wanted new check

    Difficulty 2/5 1-3 hours Newbie friendliness 78/100

    amlaban65/whyfull#27 ·

    Maintainers usually reply within 1 day

  • New check: Prometheus TSDB data outgrowing its disk
    Open
    good first issue help wanted new check

    Difficulty 2/5 Half a day Newbie friendliness 78/100

    amlaban65/whyfull#26 ·

    Maintainers usually reply within 1 day

  • Deleted-open test fails in some environments
    Possibly taken A pull request linked to this issue is open or already merged. Open
    bug good first issue help wanted

    Difficulty 3/5 Half a day Newbie friendliness 42/100

    amlaban65/whyfull#31 · 1 comment ·

    Maintainers usually reply within 1 day

  • New check: Jenkins workspaces and old build history
    Possibly taken @Sarbajit-Sengupta claimed this today. Open
    good first issue help wanted new check

    Difficulty 2/5 3-5 days Newbie friendliness 78/100

    amlaban65/whyfull#16 · 1 comment ·

    Maintainers usually reply within 1 day

  • New check: VM disk images that no libvirt VM uses
    Possibly taken @Sarbajit-Sengupta claimed this today. Open
    good first issue help wanted new check

    Difficulty 3/5 Half a day Newbie friendliness 62/100

    amlaban65/whyfull#15 · 1 comment ·

    Maintainers usually reply within 1 day

  • New check: unused Flatpak runtimes
    Possibly taken @jay23606 claimed this 1 day ago. Open
    good first issue help wanted new check

    Difficulty 2/5 1-3 hours Newbie friendliness 72/100

    amlaban65/whyfull#6 · 1 comment ·

    Maintainers usually reply within 1 day

  • New check: PostgreSQL WAL piling up (pg_wal)
    Possibly taken @arin30 claimed this 1 day ago. Open
    good first issue help wanted new check

    Difficulty 2/5 1-3 hours Newbie friendliness 82/100

    amlaban65/whyfull#4 ·

    Maintainers usually reply within 1 day

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.