Clock in and clock out with grunt-clock. Helps to keep a log of how much time you spend working with a file in your project.
by kentcdoddsJavaScript
Last 12 weeks · 0 commits
2 of 6 standards met
:rocket: commander just published version 2.8.1, so that’s now up to date in your . Check that it doesn’t break your code and release the new version of your software safe in the knowledge that it will stay in this working state. GitHub Release This pull request was created by greenkeeper.io. It keeps your software, up to date, all the time. Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster :zap:
Repository: kentcdodds/code-clock. Description: Clock in and clock out with grunt-clock. Helps to keep a log of how much time you spend working with a file in your project. Stars: 9, Forks: 4. Primary language: JavaScript. Languages: JavaScript (100%). License: MIT. Open PRs: 0, open issues: 0. Last activity: 5y ago. Community health: 42%. Top contributors: greenkeeperio-bot.
:rocket: One of your dependencies has just updated, so this PR bumps the corresponding version number in your . You can now check that the dependency update doesn't break your code, and then release the new version of your software safe in the knowledge that it will stay in this working state, regardless of _when_ your users do . Have a good day! This pull request was created by greenkeeper.io. It keeps your software, up to date, all the time. Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster :zap:
:wave: Hello! We’re all trying to keep our software up to date, yet stable at the same time. This is the first in a series of automatic PRs to help you achieve this goal. It pins all of the dependencies in your , so you have complete control over the exact state of your software. From now on you’ll receive PRs whenever one of your dependencies updates – in real time. This way you get all the benefits of up-to-date dependencies, while having them pinned at the same time. This means: No more surprises because some of your dependencies didn’t follow SemVer. Your software is always in a state you know about, regardless of _when_ someone does . If you have continuous integration set up for this repo, it’ll run automatically. Ideally, it will pass and you'll stay up to date with the press of a button. If the updated dependency _does_ break your software, it won’t affect your users, because their dependencies are still pinned to the working state. You can immediately identify which dependency updates break your software, because each one is tested in isolation. You’ll also have a branch ready to work on, so adapting to new APIs is way faster. Merge this PR and you’ll have up-to-date software without the headaches :sparkles: This pull request was created by greenkeeper.io. It keeps your software, up to date, all the time. Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster :zap: