feat(var): make count of listed vars configurable
-
Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you receive complimentary access to GitLab Duo.
Description
- feat(var): make count of listed vars configurable
Related Issues
Resolves #7749 (closed)
How has this been tested?
Before:
> glab var ls
Listing variables for the rndmh3ro/example project:
KEY PROTECTED MASKED EXPANDED SCOPE
foo false false true *
fooz false false true *
with_desc false false true *
a false false true *
a1 false false true *
a2 false false true *
a24 false false true *
a214 false false true *
a215 false false true *
a21215 false false true *
a212 false false true *
a2121 false false true *
a2121f false false true *
a2121f1 false false true *
a2121f11 false false true *
a2121f111 false false true *
a2121f1111 false false true *
a2121f11111 false false true *
a2121f111111 false false true *
a2121f1111111 false false true *
After:
> ~/dev/glab/bin/glab var ls -P 30
Listing variables for the rndmh3ro/example project:
KEY PROTECTED MASKED EXPANDED SCOPE
foo false false true *
fooz false false true *
with_desc false false true *
a false false true *
a1 false false true *
a2 false false true *
a24 false false true *
a214 false false true *
a215 false false true *
a21215 false false true *
a212 false false true *
a2121 false false true *
a2121f false false true *
a2121f1 false false true *
a2121f11 false false true *
a2121f111 false false true *
a2121f1111 false false true *
a2121f11111 false false true *
a2121f111111 false false true *
a2121f1111111 false false true *
a2121f11111111 false false true *
a2121f1111111121 false false true *
Screenshots (if appropriate):
Types of changes
-
Bug fix (non-breaking change which fixes an issue) -
New feature (non-breaking change which adds functionality) -
Breaking change (fix or feature that would cause existing functionality to change) -
Documentation -
Chore (Related to CI or Packaging to platforms) -
Test gap
Merge request reports
Activity
added Leading Organization label
Thanks for your contribution to GitLab @rndmh3ro!
🎉 - If you need help, page a coach by clicking here or come say hi on Discord.
- When you're ready, request a review by clicking here.
- We welcome AI-generated contributions and offer complimentary access to GitLab Duo!
- To add labels to your merge request, comment
@gitlab-bot label ~"label1" ~"label2"
.
This message was generated automatically. Improve it or delete it.
added Community contribution workflowin dev labels
assigned to @rndmh3ro
Reviewer roulette
Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category and by a maintainer in all other categories.
To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, mention them as you normally would! Danger does not automatically notify them for you.
Reviewer Maintainer @ck3g
(UTC+1)
@timofurrer
(UTC+1)
Generated by
🚫 DangerEdited by Danger Botadded linked-issue label
- Resolved by Timo Furrer
@gitlab-bot ready
added workflowready for review label and removed workflowin dev label
Hi
@aqualls
! Please review this documentation merge request. This message was generated automatically. Improve it or delete it.added documentation twtriaged labels
requested review from @aqualls
@aqualls, this Community contribution is ready for review.
- Do you have capacity and domain expertise to review this? If not, find one or more reviewers and assign to them.
- If you've reviewed it, add the workflowin dev label if these changes need more work before the next review.
- Please ensure the group's Product Manager has validated the linked issue.
This message was generated automatically. Improve it or delete it.
mentioned in issue gitlab-org/quality/triage-reports#22183 (closed)
mentioned in issue gitlab-org/quality/triage-reports#22185 (closed)
added featureenhancement groupcode review labels
changed milestone to %17.9
added typefeature label
added devopscreate sectiondev labels
requested review from @ekigbo
added Technical Writing label
removed twtriaged label
Approved from a Technical Writing perspective, @rndmh3ro. I'll leave the rest of the review to Ezekiel.
Reviewer roulette
Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category and by a maintainer in all other categories.
To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, mention them as you normally would! Danger does not automatically notify them for you.
Reviewer Maintainer @ck3g
(UTC+1)
@timofurrer
(UTC+1)
Generated by
🚫 DangerEdited by ****- Resolved by Timo Furrer
mentioned in issue gitlab-org/quality/triage-reports#22297 (closed)
mentioned in issue gitlab-org/quality/triage-reports#22375 (closed)
requested review from @timofurrer and removed review request for @ekigbo
- Resolved by Sebastian Gumprich
changed milestone to %17.10
added 57 commits
- 75281c8e...7ab36ce5 - 47 earlier commits
- 7b26f065 - fix: accept input from stdin when stdin is TTY
- a41f0cf9 - test: create with multiple files
- f8e65d24 - feat: show help hint on error instead of full usage
- 593ff709 - feat(ci status): return error when pipeline failed
- 6c21c329 - feat(ssh-key): add usage type to output
- 5ed9992b - fix(token-list): token list works outside a repository
- ed25ca75 - fix(ci status): allow live to loop with NO_PROMPT
- b3960473 - chore(deps): update module github.com/spf13/cobra to v1.9.1
- 687c4982 - chore(deps): update module golang.org/x/crypto to v0.33.0
- 50921df9 - add more tests
Toggle commit listadded 104 commits
-
50921df9...648db314 - 103 commits from branch
gitlab-org:main
- 0683d10f - Merge branch 'main' into 'feat/var_ls_p'
-
50921df9...648db314 - 103 commits from branch
mentioned in issue gitlab-org/quality/triage-reports#22481
started a merge train
@rndmh3ro thanks for the contribution! I've approved and started the merge train
🚅 🎉 mentioned in commit ec23203f
Hi @rndmh3ro
👋 🎉 See where you rank! Check your spot on the contributor leaderboard and unlock rewards.
How was your code review experience with this merge request? Please tell us how we can continue to iterate and improve:
- React with a
👍 or a👎 on this comment to describe your experience. - Create a new comment starting with
@gitlab-bot feedback
below, and leave any additional feedback you have for us in the comment.
As a benefit of being a GitLab Community Contributor, you have access to GitLab Duo, our AI-powered features. With Code Suggestions, Chat, Root Cause Analysis and more AI-powered features, GitLab Duo helps to boost your efficiency and effectiveness by reducing the time required to write and understand code and pipelines. Visit the GitLab Duo documentation to learn more about the benefits.
Thanks for your help!
❤️ This message was generated automatically. Improve it or delete it.
- React with a