A practical framework for building consistency, contributing to open source, and growing through small actions every day.
This repository started as my one-commit-a-day challenge: showing up every day and making a small contribution to keep moving forward.
It has since evolved into a collection of:
- open source contribution practices
- daily, weekly, and monthly logs
- guided reflections
- technical TO-BE journaling
- project and experiment templates
- practical resources and lessons learned
The goal is simple:
Show up. Make progress. Reflect. Repeat.
One Commit a Day is meant to grow with you. Start with simple practice of showing up and making one small contribution, then use the logs, and reflections, and journals as you want to go deeper.
Open the current year's folder:
logs/
└── 2027/
├── README.md
├── calendar.md
├── daily/
├── weekly/
└── monthly/Use:
calendar.mdfor a quick view of your yeardaily/to record small contributionsweekly/to step back and reflectmonthly/to look for patterns and direction
It can be code, documentation, an issue, a review, discussion, learning, or work on your own project. It doesn't have to be a commit.
Use the daily log to capture what you actually worked on.
When you want to think beyond today's tasks, explore:
- journal/technical-to-be.md - Who do I want to become?
- journal/ai-and-technology.md - How do I want to relate to changing technology?
- journal/technical-practice.md - How do I want to practice, work, and learn?
The templates provide lightweight formats for:
- Daily logs
- Weekly reflections
- Monthly reflections
- Project logs
- Experiment logs
You don't need a perfect system. Just start showing up.
A “contribution” is defined as any action that helps move a project forward or deepens your involvement. A contribution does not have to be a major feature or a merged pull request.
It can include:
- Code
- Documentation
- Issues
- Discussions
- Reviews
- Bug investigation
- Learning and researching
- Work on your own projects
The goal is not perfection, but consistency.
By showing up regularly, even in small ways, you can:
- build real experience in open source collaboration
- develop technical and communication skills
- build confidence through repeated practice
- discover what kind of technical work matters to you
- grow into a long-term contributor
Important
The goal is not to extend a contribution streak or make your GitHub contribution graph greener. The grass may look greener on someone else's GitHub graph, but what matters is making meaningful progress in your own journey, even when that progress is small.
For busy days.
- Comment on an Issue (ask, clarify, suggest)
- Review someone’s PR (even small feedback)
- Improve README / fix typo
- Work on private repositories
The normal target.
- Submit an Issue
- Prepare or edit a PR for submission
- Reproduce a bug + document it
- Add example usage / test case
- Improve documentation clarity
- Make meaningful progress on your own repository
Larger contributions, typically 1–2 times a month or every other month.
- Submit a PR (bug fix, doc improvement)
- Implement a new feature or significant improvement
- Refactor a complex code section
- Write a detailed tutorial or guide
- Lead a discussion or proposal for a new design or feature
- Create or significantly improve a repository
Every day = at least Level 1
1–2 days a week = Level 2
1–2 days a month = Level 3
The levels are guidelines.
Life gets busy.
Work, travel, unexpected life events, low energy, or other responsibilities can make a normal contribution unrealistic.
Recovery Mode exists to protect consistency without encouraging burnout.
Recovery Mode (Level 1 — Last Resort Only):
- Read an issue or PR and leave a thoughtful comment
- Review a repository’s structure or contribution guidelines
- Read code and write at least one insight in the daily log
- Star a useful project and explore it briefly
- (Optional) Work on a private repository
Rules:
- Use only when time or energy is very limited
- Still log the activity
Here is a simple daily loop:
⏰ 30–60 min routine
- Open a developer platform, such as GitHub
- Pick one small thing
- Work for roughly 30–60 minutes when possible
- Make a contribution
- Log what you did
- Reflect when useful
Show Up → Contribute → Log → Reflect → Repeat
That's all.
Inspired by the idea of a Japanese diary system, this section invites you to move beyond tracking what you do and reflect on who you are trying to become.
One Commit a Day is not only about what you accomplish.
Over time, repeated work raises more important questions:
What kind of technical person do I want to become?
The TO-BE Journal section explores questions such as:
- Why am I in the technology field, and what matters to me?
- What problems do I want to solve and who do I want to help?
- How do I want to relate to technology, AI, and my own practice?
- What kind of technical person do I want to become?
The purpose is not to create a perfect career plan.
It is to develop a clearer sense of direction.
What do I need to do today?
What kind of developer do I want to be while doing it?
The two can coexist.
The repository separates thinking about your direction from recording what actually happened.
For thinking about:
- Who you want to become
- What matters to you
- How you relate to AI and technology
- How you want to learn, work, and contribute
Reusable formats for:
- Daily logs
- Weekly reflections
- Monthly reflections
- Project logs
- Experiment logs
Yearly records of what you actually did, learned, and reflected on.
This creates a simple loop:
Show Up → Contribute → Log → Reflect → Learn → Grow
You don't need to complete every journal or template. Use what is useful to you.
Each year provides a ready-to-use structure so you can start logging immediately without creating your own system.
logs/
└── 2027/
├── README.md
├── calendar.md
├── daily/
├── weekly/
└── monthly/The yearly README provides space to think about the beginning and the end of the year. The calendar.md provides a visual record of:
- 🌱 TO-BE
- ✅ Showing up / making progress
- 💻 Technical work
- 📚 Learning
- ⭐ Major events or milestones
- 🔥 Busy periods
- 🚀 Focused work periods
- ✨ Memorable moments
The daily, weekly, and monthly logs provide different ways to reflect on your work and growth.
The long-term goal is not simply to accumulate commits.
It is to move from:
Show up → Participate → Contribute → Collaborate → Become a trusted contributor
A possible progression:
Discover projects, communities, technologies, and areas that interest you.
Choose a few projects and become familiar with their codebase and community.
Take on larger issues, support other contributors, and eventually propose improvements of your own.
The objective is to build relationships, experience, trust, and technical depth over time.
It's easy to think:
I need to make a big and valuable contribution.
But meaningful open source involvement can also come from:
Showing up consistently and contributing in small ways.
Because in open source:
- Consistency builds reputation over time.
- Repeated interaction builds trust with maintainers.
- Engagement and presence matter as much as code.
- Long-term involvement creates opportunities to contribute more deeply.
See DISCLAIMER.md for important notes about using this framework.
For now, ideas, suggestions, and feedback are welcome through Issues. If you have an idea for improving the system, feel free to open an issue.