How Do You Decide Which Daily Tasks to Automate?

[renvikzylar4-creator]

Discussion Type

Product Feedback

Discussion Content

I'm curious how developers decide which repetitive tasks are worth automating and which are better handled manually.

I work in medical billing with Avenue Billing Services, where routine tasks can involve checking information, reviewing records, and keeping details organized. It makes me wonder how small scripts or simple tools could reduce repetitive work without creating extra maintenance.

For those who use GitHub for personal or professional projects, what kinds of tasks have you successfully automated?

Do you usually start with a small script, build a reusable tool, or look for an existing open source project? I’d love to hear what has saved you the most time.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[kriszwart]

Great question. As a solo builder my rule of thumb is: if I've done the same thing by hand three times and it follows the same steps each time, it's a candidate. If it needs judgement every time, I leave it manual or just add a checklist.

I nearly always start with a small script in the repo and let it prove itself for a few weeks. Only if it keeps earning its keep does it become a proper tool or a GitHub Action. Before building anything I have a quick look for an existing open source project, since maintenance is the real cost, not the first build.

The biggest time savers for me have been scheduled Actions for routine checks, templates for repeated docs and issues, and lately AI agents for the "read this, tidy that" type of work. For records-heavy work like billing, I'd start with validation scripts that flag problems rather than ones that change data automatically. Much safer, and you keep a human in the loop.

What's the most repetitive bit of your day at the moment?

[onionroots]

As a Flutter developer, I usually look for tasks that I repeat across multiple projects, such as API integration setup, model generation, boilerplate code, and build or release checks.

My approach is to automate a task when it follows predictable steps and takes time away from actual development. I usually start with a small script or an existing tool before building something more complex. For example, GitHub Actions can automate tests and basic code quality checks whenever new code is pushed.

I also believe not everything should be automated. When a task requires human judgment or could affect production data, I prefer keeping manual review in the process.

For me, the best automation is one that saves time consistently without adding unnecessary maintenance.