-
-
Notifications
You must be signed in to change notification settings - Fork 242
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add start --no-gap
and stop --at
#254
Conversation
This commit adds the functionality needed to catch up on time tracking. Take the scenario where you are engaged in several ad hoc discussions at the desks of your colleagues, seamlessly transitioning into each other. While you manage to remember when each discussion start, you still need to enter those into Watson. This commit gives you the tools to do so conveniently. You can use watson stop --at to specify when a event stopped and watson start --no-gap to instruct Watson to start the new event seamlessly to the one most recently stopped. By this to catch up on your time tracking all you need to do is to cycle through these two commands.
In case you do not like the git history of #236, I created this branch to serve as a single commit version of the feature. It can be cherry-picked/fast-forward merged, leading to a linear history. Some prefer those. Please note that I am much more in favour of the actual development history of #236 as it offers many atomic commits and some insights in the development process. |
I've rebased the work in #236 and merged it. For external contributions, I prefer having a single commit feature or fix and keep a linear comprehensive history. But I understand your point. Thanks again for your work! |
Added: - New `add` command (#202) - Add lunar start time options to the `report` and `log` commands (#215) - Aggregate reports by day (#231) - Fish shell completion (#239) - Add support for first day of the week configuration in reports and logs (#240) - Python 3.7 support (#241) - Add `start --no-gap` and `stop --at` options (#254) Changed: - The `edit` command now checks data consistency (#203) - Current state saving is now improve when using Watson as a library (#214) - Prevent calling `get_start_time_for_period` multiple times (#219) Fixed: - Improved support for UTF-8 with Python 2 (#211) - Zsh completion for tags and projects with spaces in their names (#227) - Typos in commands output (#230, #235) - Project URL of the project in PyPI (#260) Removed: - Python 3.3 support (#210).
Added: - New `add` command (#202) - Add lunar start time options to the `report` and `log` commands (#215) - Aggregate reports by day (#231) - Fish shell completion (#239) - Add support for first day of the week configuration in reports and logs (#240) - Python 3.7 support (#241) - Add `start --no-gap` and `stop --at` options (#254) Changed: - The `edit` command now checks data consistency (#203) - Current state saving is now improve when using Watson as a library (#214) - Prevent calling `get_start_time_for_period` multiple times (#219) Fixed: - Improved support for UTF-8 with Python 2 (#211) - Zsh completion for tags and projects with spaces in their names (#227) - Typos in commands output (#230, #235) - Project URL of the project in PyPI (#260) Removed: - Python 3.3 support (#210).
Added: - New `add` command (#202) - Add lunar start time options to the `report` and `log` commands (#215) - Aggregate reports by day (#231) - Fish shell completion (#239) - Add support for first day of the week configuration in reports and logs (#240) - Python 3.7 support (#241) - Add `start --no-gap` and `stop --at` options (#254) Changed: - The `edit` command now checks data consistency (#203) - Current state saving is now improve when using Watson as a library (#214) - Prevent calling `get_start_time_for_period` multiple times (#219) Fixed: - Improved support for UTF-8 with Python 2 (#211) - Zsh completion for tags and projects with spaces in their names (#227) - Typos in commands output (#230, #235) - Project URL of the project in PyPI (#260) Removed: - Python 3.3 support (#210).
This commit adds the functionality needed to catch up on time tracking.
Take the scenario where you are engaged in several ad hoc discussions at
the desks of your colleagues, seamlessly transitioning into each other.
While you manage to remember when each discussion start, you still need
to enter those into Watson.
This commit gives you the tools to do so conveniently. You can use
to specify when a event stopped and
to instruct Watson to start the new event seamlessly to the one most
recently stopped. By this to catch up on your time tracking all you need
to do is to cycle through these two commands.