proposal: new command tea times
#50
Labels
No Label
kind/breaking
kind/bug
kind/build
kind/dependency
kind/deployment
kind/docs
kind
enhancement
kind
feature
kind/proposal
kind
question
kind
refactor
kind/security
kind/testing
kind/translation
priority/critical
priority/high
priority/low
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/has-backport
status/has-pull
status/needs-backport
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
upstream/sdk
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/tea#50
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add a new command:
tea times
(ortea time
depending on #37 , no pun intended), which shows the tracked times.This would make the time tracking feature usable in the first place for things like billing, as the web frontend doesn't provide a meaningful interface yet (tracked in https://github.com/go-gitea/gitea/issues/8684).
syntax
semantics
We can make the command dead simple, or have smart semantics:
simple version
tea times [user]
lists tracked times of the current repo. When a user is specified, only their times will be listed. When not in a repo (or no-r
flag provided), it fails.smart version
tea times [user]
behaves as abovetea times
lists all tracked times of the logged-in user across repos (/api/v1/user/times
). The[user]
parameter is meaningless here.discussion
I'm not sure if different semantics within the same syntax are a good idea, as the parameters differ. What is your impression?
What would be a good time filter format? ISO Dates are hard to type. Does golang provide a good human time parsing library (eg
--from='1 month ago'
)?I'd be willing to implement this, but have no ETA.
noerw referenced this issue2019-10-25 14:35:48 +00:00
noerw referenced this issue2019-10-25 21:42:03 +00:00
#54 closed this