-
Notifications
You must be signed in to change notification settings - Fork 76
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
Readme #149
Readme #149
Conversation
Sorry, it seems I have also included my commit for another issue into this PR. This is the first project that I'm submitting PRs for so apologies for the repeat commit. I'm not sure how to undo/rectify this repetition; would appreciate it greatly if someone could kindly provide some guidance on this! |
Hi, thanks for your PRs, That's no problem, we will handle this :-) (edit: actually when your other PR is merged, it won't matter anymore as git is very smart :-) |
That's good to know, thanks! |
@jwnpoh: #147 is now merged. This means that you can update your timetrace fork and then merge Edit: I think you don't have to do this; only if you want to. |
Thanks for the pointers! I'll give it a try even if only just to get a better grasp of how branching and merging works. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Nice, as you can see your merge created a merge commit and the confirmation-related changes don't appear as difference anymore, because they're now included in the target branch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This PR is included in timetrace v0.11.1. |
Addresses #148.