The one with `-f` for push, and a new `timelog` command
2 new features in this release.
-f
for the push
command.
Previously, trying to push
anything within the app
folder was a hard error. This is needed since the syncing mechanism can get really screwed up when you're trying to run delete commands in the container (which then causes the host file to get deleted)...
However, since the syncing is still not 100% reliable, we've added -f
to allow the error to be downgraded to a friendly warning. This means the following is now possible.
wf2 push app/code/somefile.php -f
new timelog
command.
This will likely be pulled into a separate tool once we have feedback etc, but it's been added to wf2 since we all have it installed already and are familiar with it.
The primary goal is to allow you to view jira worklogs, grouped into days.
The following will show a summary of today + 1 prev day (2 in total)
wf2 timelog 2d
[wf2 info] getting your account info...
[wf2 info] getting issues & worklogs for 2 day(s)
+-------------------+--------+--------+----------+
| Date | Total | Normal | Overtime |
+-------------------+--------+--------+----------+
| Sat, 09 Nov, 2019 | 4h 0m | 0h 0m | 4h 0m |
| Fri, 08 Nov, 2019 | 7h 30m | 7h 30m | 0h 0m |
+-------------------+--------+--------+----------+
if you provide the -v
flag, you'll get more verbose output
wf2 timelog 2 -v
+------------------------------------------------------------------------------+
| Date | Normal | Overtime | Total |
| -------------------+--------+----------+------- |
| Fri, 08 Nov, 2019 | 7h30m | 0h0m | 7h30m |
+------------------------------------------------------------------------------+
| Ticket | Time | Type | Status |
| -----------------------------------------------+------+--------+------------ |
| https://acme.atlassian.net/browse/ACME-943 | 30m | Normal | UAT |
| https://acme.atlassian.net/browse/ACME-912 | 7h | Normal | Refinement |
+------------------------------------------------------------------------------+
First run
The very first time you run the command, you'll need --api
--email
& --domain
where
api
is a personal Jira API key (make your own in the user section of jira)email
is the email used in your jira accountdomain
is the sub-domain of your cloud account, eg, if you accesshttps://acme.atlassian.net
then yours isacme
# first time only
wf2 timelog 1 --api 123456 --email [email protected] --domain acme