-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
updated shell completion #368
Conversation
|
@rsteube Tests are kinda fucky right now due to some changes on gitlab.com, I'm going to go ahead and merge this on faith since you've consistently delivered in the past. Also if you're interested in gaining contributor access so you can bring these through a little easier I'm super open to that. |
Actually, ideally lets move the action package into |
What does contributor access do? I am rather worried if means i can accidentally push to the wrong remote XD. |
I managed to adapt this for |
@rsteube Looks like the PR I just merged caused a conflict in this. Can you update and we'll get it brought in? |
Contributor access would let you merge, I don't think anyone can push to master, but I would need to double check the controls |
Ok, thats fine then - i probably have to to fix some small quirks anyway when people start using it. |
@rsteube I've added you as a collaborator. Not sure the state of the tests, so I (or someone) may need to fix those, ideally you'll be able to merge this on your own and bring in updates at your discretion |
I can see the ci stuff is pretty borked at this point, and I introduced some conflicts bringing in a few other changes. Let's get the conflicts resolved and I'll bring this in and work to fix the pipelines so we can release |
Nice - yeah at least at one point the url simply changed. I think it was sth like an added slash another "breadcrumb" in the repository url. (regarding the tests) |
@zaquestion seems the conflict was just an additonal import. Apart from that the build itself is ok - shall i do a rebase first? |
Ok, seems updating that wasn't too hard. But now https://gitlab.com/lab-testing/test/-/merge_requests/1385 already exists, so the test fails. |
Codecov Report
@@ Coverage Diff @@
## master #368 +/- ##
==========================================
+ Coverage 63.56% 63.61% +0.04%
==========================================
Files 49 50 +1
Lines 2709 2850 +141
==========================================
+ Hits 1722 1813 +91
- Misses 857 893 +36
- Partials 130 144 +14
Continue to review full report at Codecov.
|
@zaquestion well, the travis build exited with 0 but it still isn't reported. |
moved ci fixes to separate PR: #386 |
@rsteube I think I got the travis stuff running again, I've gotta wait for a the checks to run on a PR before I can make them required, go ahead and try updating this branch to the latest they should run |
Verfied the tests are passing with your fixes as well https://travis-ci.org/github/zaquestion/lab/builds/719466634 |
- uses github.com/rsteube/carapace - thus no need for cobra fork anymore - replaced completion_function.go with go callbacks - provides shell completion for bash, elvish, fish, powershell and zsh
Had another go at what i originally extracted from the cobra zsh PR: https://github.com/rsteube/cobra-zsh-gen
This brings lab back to cobra (no fork) and makes the completion less cryptic as it's all go code.
Needs some good testing (looks ok so far).
fixes #333
fixes #367