[EDIT: As shanaqui notes below this post, my suggestions here are mostly manual, not automated. My point here is to explore some creativity of goal wordings.]
As another way to word a goal, let’s call the plan “Commit1” = “at least one commit per day”, and that would only be [manually] incremented once each day. You could put the total number of commits in the description. One can freely update the corresponding data description at any time, even after the day is over, so you could keep a running total in there or update whenever it’s most convenient. The downside is that you don’t get the fun and motivating beeminder graph of that data.
You could have another goal called commit2 to tally up the total number of commits. So commit1 would make sure that you commit everyday, while commit2 tracks your progress and gets way ahead.
So let’s say you start your day and you make one commit. You would increment both commit1 and commit2. All further commits during that day would just increment commit2. Commit2 tends to get ahead, and you can ratchet it whenever you want.
You can also set the rate of commit1 to 0.9. You still increment by one each day, but every 10 days you’ll get a buffer day, which is nice to have for sick days. If you find that you can ride the graph up consistently everyday even with one or more buffer days, that’s a nice feeling. If you ever feel like you have gained too many buffer days, you can always ratchet those back down.
The options are really endless according to your creativity. Commit1 could be “uptick on commit #1, #21, #41, etc.” meaning that you’ll increment commit1 on your first commit, but also on your 21st, 41st, etc. This would allow you to work extra hard one day to get a day off. When I said “21,41,etc”, that’s just an example. You can make that schedule beyond what would normally occur in a day, so it would only happen if you do an extraordinary day.
Or you could make commit1="first commit of day or commit2 cumulative=1000,2000,3000,etc " so you give yourself a bonus buffer day after you’ve achieved some milestones. While it would be easier to track commit2 as it’s own beeminder goal, that value could be tracked inside the commit1 description field.
Another way to word this for commit1 is “First commit or bonus, see fine details.” Then describe the bonus structure in the fine details field.