September 20th, 2024

Disabling Scheduled Dependency Updates

David Lord addresses challenges in managing dependency updates for his GitHub libraries, opting for local updates to reduce notification clutter and improve focus, while developing a tool called gha-update for GitHub Actions.

Read original articleLink Icon
Disabling Scheduled Dependency Updates

David Lord discusses the challenges of managing scheduled dependency updates for his numerous GitHub libraries. He notes that while maintaining a consistent development environment is crucial, the influx of automated pull requests (PRs) from tools like Dependabot and pre-commit.ci can be overwhelming, especially for stable projects with low activity. Each project can generate multiple PRs monthly, leading to a cluttered notification system that obscures important updates and makes it difficult for contributors to engage meaningfully. To mitigate this, Lord has disabled scheduled updates and instead opted for a local update command, allowing him to manage dependencies when actively working on a project. He created a tool called gha-update to facilitate local updates for GitHub Actions, which previously lacked a straightforward local update method. This approach allows him to maintain a clean workflow, ensuring that he only addresses updates when necessary, thus avoiding the noise of constant notifications. By implementing this system, he has successfully streamlined his dependency management process, allowing for a more focused and efficient development environment.

- Scheduled dependency updates can overwhelm maintainers of stable projects.

- Disabling automated updates can reduce notification clutter and improve focus.

- Local update commands allow for more controlled dependency management.

- A custom tool, gha-update, was developed to facilitate local updates for GitHub Actions.

- This approach enables maintainers to address updates only when actively working on a project.

Link Icon 4 comments
By @ydnaclementine - 4 months
This guy calls it out here, but I will say that the notifications page on github could do with a redesign. If you're in a busy org for your job, it's not easy to see everything in the org (they limit showing number of notifications per repo), and the volume of notifications from your job org will cover up anything in your personal/following repos.

Sure you could unfollow work repos you aren't interested in, but you're automatically following any new ones.

By @maximilianroos - 4 months
An alternative is to automatically merge dependency changes which pass the tests. Then there's no need for any intervention unless something needs your attention, just dismiss the notification.

We do this at PRQL, with: https://github.com/PRQL/prql/blob/12b1bb65afd5b67f34b98d0ac1...

By @cesnja - 4 months
You get to choose either the mind-numbing churn of constant updates, the risk of updates piling up and becoming unmanageable, or shipping software with vulnerabilities. None of these options sounds fun.
By @donatj - 4 months
I really wish there was a step before opening a PR, like a page with a list of what's out of date that let's you click a button to open a PR for one or more dependency updates.