v0.1.30

Provide list releases for a project. gr rl list command. Implemented for Github in this iteration.

Ex:

• gr rl list List the releases associated with a project. Tag, description, URL, etc...

v0.1.29

Provide option to format output in JSON format.
Ex.

• gr pp list --format json List all pipelines/actions in JSON format, one JSON per line.

v0.1.28

Provide a --format argument for list operations. Defaults to pipe, .i.e it separates the fields with " | ". We can also format the output with CSV .i.e ",".

Ex:

• gr pp list --format csv - Lists all pipelines/actions in your repository separating the fields with commas.

v0.1.27

Include the title when listing pull requests.

v0.1.26

Provide retrieval of image tag metadata given a registry repository id. Gitlab only for now.

Eg.

• gr dk image --repo-id 1 v0.0.1 it will retrieve the date the image was created, path and its short SHA.

v0.1.25

Implements logic for docker command list operation flags --num-pages and --no-headers. Gitlab only for now.

Eg:

• gr dk list --repos --num-pages List number of registry repository pages available
• gr dk list --tags --repo-id 10 --num-pages List number of image tag pages available given the registry repository id

v0.1.24

Make use of --sort desc if provided on the cli. It was default to asc in all cases.

v0.1.23

Provide a command to list project Docker registry repositories and image tags. Gitlab implementation for now.

Ex:

• gr dk list --repos List registry repositories for the given project
• gr dk list --tags --repo <id> List image tags for the given repository id

v0.1.22

Provide a --created-before for list operations.

Ex:

• gr mr list --created-before 2024-02-01T00:00:00Z merged Lists merged pull requests that were merged before that date. This pulls up to max_pages for the pull requests api or if not specified application global default of 10. Rate limits are automatically inspected on the headers and the application might stop processing if we approach the rate limit. Safety threshold of 10 requests before hitting the limit. Filtering is post API call, so the data being pulled might not be complete, so doing inspection with --page, --from-page, --to-page might be needed.

It can be combined with --created-after.

v0.1.21

Provide list option --created-after and sort asc by creation time by default. --sort option provided if one wants to sort in descending order.
Ex:

• gr pp list --created-after 2024-01-01T00:00:00Z lists pipelines/actions after that date.

Filtering is done post API, so the data being pulled up to max number of pages might not be all the data that meets the created-after requirement. One could pull the rest by inspecting pages with --page, --from-page, --to-page options and tweak max pages for the API accordingly. If there is a lot of data, one can wrap gr pp list and iterate over the pages with --from-page, --to-page. Remote rate limits are inspected on headers, so if one needs to pull lots of data, doing it in chunks with a sleep operation in between gr calls to respect those limits would be an approach to consider.