gitlabtime issueshttps://ce.cusy.io/oss/gitlabtime/-/issues2024-03-28T17:33:26Zhttps://ce.cusy.io/oss/gitlabtime/-/issues/29Rename url option2024-03-28T17:33:26ZVeit Schieleveit.schiele@cusy.ioRename url optionIt should be possible to address the host both via the name and the URL, for example with
* `pipenv run gitlabtime --host https://ce.cusy.io`
* `pipenv run gitlabtime --host cusy` oder `pipenv run gitlabtime --host "cusy GitLab"`
if...It should be possible to address the host both via the name and the URL, for example with
* `pipenv run gitlabtime --host https://ce.cusy.io`
* `pipenv run gitlabtime --host cusy` oder `pipenv run gitlabtime --host "cusy GitLab"`
if the following is defined in the [configuration file](#4):
``` toml
[host "cusy"]
url = "https://ce.cusy.io"
```
* The first host defined in the [configuration file](#4) is the default value.Thomas LotzeThomas Lotzehttps://ce.cusy.io/oss/gitlabtime/-/issues/28csv files2024-03-28T17:21:35ZVeit Schieleveit.schiele@cusy.iocsv files* The default should be that a csv file is written.
* Standard file names should look something like this:
* `host_2024-02`
* `host_path-to_2024-02`
* `host_path-to_veit_2024-02`
* `host_path-to_veit_from-2024-02-01`
* `ho...* The default should be that a csv file is written.
* Standard file names should look something like this:
* `host_2024-02`
* `host_path-to_2024-02`
* `host_path-to_veit_2024-02`
* `host_path-to_veit_from-2024-02-01`
* `host_path-to_veit_from-2024-02-01-to-2024-02-29`
## Storage location
* The csv files should be written to a configurable storage location.
* The default for the storage location should be `data`.
* `data` should be present, but all content should be ignored by Git.
* It should be possible to change the default value in the CLI, for example with
``` bash
pipenv gitlabtime --data "/PATH/TO/DATA"
```
oder
``` bash
pipenv gitlabtime --data "../PATH/TO/DATA"
```
* It should be possible to change the storage location in the [configuration file](#4), for example with
``` toml
[core]
data = "PATH/TO/DATA"
```Thomas LotzeThomas Lotzehttps://ce.cusy.io/oss/gitlabtime/-/issues/27Simplify the specification of the time period2024-03-28T13:00:46ZVeit Schieleveit.schiele@cusy.ioSimplify the specification of the time periodThe period should only be specified with `--period` and no longer with `--start`, `--end` and `--month`.
Possible values should be:
* `2024`
* `2024-02`
* `2024-02-29`
* `"last year"`
* `"this year"`
* `"last month"`
* `"this month"`
* ...The period should only be specified with `--period` and no longer with `--start`, `--end` and `--month`.
Possible values should be:
* `2024`
* `2024-02`
* `2024-02-29`
* `"last year"`
* `"this year"`
* `"last month"`
* `"this month"`
* `"last week"`
* `"this week"`
* `"yesterday"`, `yesterday`
* `"today"`, `today`
* `"from 2024-02-01"`
* `"to 2024-02-29"`
* `"from 2024-02-01 to 2024-02-29"`
The default value should be `"last month"`.
The default value should be configured in the [configuration file](#4), for example with:
``` toml
[core]
period = "today"Thomas LotzeThomas Lotzehttps://ce.cusy.io/oss/gitlabtime/-/issues/26path Option2024-03-28T12:11:18ZVeit Schieleveit.schiele@cusy.iopath OptionIt should be possible to address individual groups or user projects precisely, for example with `gitlabtime --path oss/gitlabtime` or `gitlabtime -p veit/gitlabtime`.
This should presumably replace the conflict-prone `--project` and `--...It should be possible to address individual groups or user projects precisely, for example with `gitlabtime --path oss/gitlabtime` or `gitlabtime -p veit/gitlabtime`.
This should presumably replace the conflict-prone `--project` and `--group` options.
The default value should be `.`.Thomas LotzeThomas Lotzehttps://ce.cusy.io/oss/gitlabtime/-/issues/25Cache token2024-03-28T11:54:52ZVeit Schieleveit.schiele@cusy.ioCache token* The token should be cached 30m by default.
* The caching time should be changed, for example with `gitlabtime credential.helper Cache` and `gitlabtime credential.helper 'Cache timeout=3600'`.
* This should write a [configuration file](...* The token should be cached 30m by default.
* The caching time should be changed, for example with `gitlabtime credential.helper Cache` and `gitlabtime credential.helper 'Cache timeout=3600'`.
* This should write a [configuration file](#4), for example with
```toml
[credential]
helper = "Cache"
cache-timeout = "3600"
```Thomas LotzeThomas Lotzehttps://ce.cusy.io/oss/gitlabtime/-/issues/23403 Forbidden for projects without repository2024-03-28T10:36:45ZVeit Schieleveit.schiele@cusy.io403 Forbidden for projects without repositoryWhen requesting the API with `$ pipenv run gitlabtime --url https://ce.cusy.io/` , I get the following message for various projects:
```
403 Forbidden
```
This seems to happen for all projects without a git repository.When requesting the API with `$ pipenv run gitlabtime --url https://ce.cusy.io/` , I get the following message for various projects:
```
403 Forbidden
```
This seems to happen for all projects without a git repository.Thomas LotzeThomas Lotzehttps://ce.cusy.io/oss/gitlabtime/-/issues/20Optimisation: cut off API queries for old entries2024-03-28T10:41:02ZThomas LotzeOptimisation: cut off API queries for old entriesThomas LotzeThomas Lotzehttps://ce.cusy.io/oss/gitlabtime/-/issues/15Project management2024-03-28T10:46:13ZThomas LotzeProject managementA place to track time spent other than developing.A place to track time spent other than developing.Thomas LotzeThomas Lotzehttps://ce.cusy.io/oss/gitlabtime/-/issues/14Issue checking report2024-03-28T10:41:53ZThomas LotzeIssue checking reportReport on issues with activity during time span, compare time spent with time estimated (wrt. end of time span).Report on issues with activity during time span, compare time spent with time estimated (wrt. end of time span).Thomas LotzeThomas Lotzehttps://ce.cusy.io/oss/gitlabtime/-/issues/7Add proper documentation2024-03-28T10:47:32ZThomas LotzeAdd proper documentationVeit Schieleveit.schiele@cusy.ioVeit Schieleveit.schiele@cusy.iohttps://ce.cusy.io/oss/gitlabtime/-/issues/6Test coverage, GitLab CI/CD Pipeline and Badge2024-03-28T10:56:54ZThomas LotzeTest coverage, GitLab CI/CD Pipeline and Badge* [Test coverage visualization](https://docs.gitlab.com/ee/ci/testing/test_coverage_visualization.html#python-example)
* [View code coverage results in the MR](https://docs.gitlab.com/ee/ci/testing/code_coverage.html#view-code-coverage-r...* [Test coverage visualization](https://docs.gitlab.com/ee/ci/testing/test_coverage_visualization.html#python-example)
* [View code coverage results in the MR](https://docs.gitlab.com/ee/ci/testing/code_coverage.html#view-code-coverage-results-in-the-mr)
* [Badge](https://python-basics-tutorial.readthedocs.io/en/latest/test/coverage.html#badge)Thomas LotzeThomas Lotzehttps://ce.cusy.io/oss/gitlabtime/-/issues/4Config file2024-03-28T17:33:27ZThomas LotzeConfig fileFor example, a `~/.gitlabtime` or `~/.config/gitlabtime/config` file:
```toml
[core]
data = "PATH/TO/DATA"
[host "cusy"]
url = "https://ce.cusy.io"
[credential]
helper = "Cache"
cache-timeout = "3600"
```For example, a `~/.gitlabtime` or `~/.config/gitlabtime/config` file:
```toml
[core]
data = "PATH/TO/DATA"
[host "cusy"]
url = "https://ce.cusy.io"
[credential]
helper = "Cache"
cache-timeout = "3600"
```Thomas LotzeThomas Lotze