Skip to content
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

Should pipelineresource be grouped in the list #148

Closed
vdemeester opened this issue Jul 3, 2019 · 4 comments · Fixed by #351
Closed

Should pipelineresource be grouped in the list #148

vdemeester opened this issue Jul 3, 2019 · 4 comments · Fixed by #351
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. kind/question Issues or PRs that are questions around the project or a particular feature

Comments

@vdemeester
Copy link
Member

Do we want to group pipelineresource by type in tkn pipelineresource list ? Or do we want to add an option for that ?

/cc @siamaksade @sthaha

Based on https://github.com/tektoncd/cli/pull/128/files#r297645542

/kind question
/kind feature

@tekton-robot tekton-robot added kind/question Issues or PRs that are questions around the project or a particular feature kind/feature Categorizes issue or PR as related to a new feature. labels Jul 3, 2019
@siamaksade
Copy link

Makes sense to me. Grouping means to show as separate blocks or rather sort on type, and then creation time?

@vdemeester
Copy link
Member Author

Makes sense to me. Grouping means to show as separate blocks or rather sort on type, and then creation time?

I would pictures it like that yes

@hrishin
Copy link
Member

hrishin commented Jul 4, 2019

Yes. Would be also nice to filter resources by one or more types like tkn list resources -t ImageResource

@piyush-garg
Copy link
Contributor

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. kind/question Issues or PRs that are questions around the project or a particular feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants