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

Fix styling on 0.73 release notes #714

Merged
merged 1 commit into from
Dec 27, 2022
Merged

Conversation

sholderbach
Copy link
Member

  • fix heading levels
  • use shell style consistently
  • clarify phrasing on the breaking changes

- fix heading levels
- use shell style consistently
- clarify phrasing on the breaking changes
@kubouch kubouch merged commit 529e0d4 into nushell:main Dec 27, 2022
@sholderbach sholderbach deleted the style-fix-rn73 branch December 27, 2022 21:09
ayax79 pushed a commit to ayax79/nushell.github.io that referenced this pull request Jun 26, 2024
Hi! I added completion to `gh pr checkout <tab>`
It grabs the first 30 open prs 


![image](https://github.com/nushell/nu_scripts/assets/30557287/755fe63b-dc22-49ef-89c3-27e1ba115d68)

### I tried some things
`gh pr checkout` can accept
- a pr number
- a url
- or a branch

before I tried
- Incrementing the limit of PRs from 30 (default) to 50, but I takes
considerably longer to query, and _gotta go fast_
- using the `extra` field in autocomplete
[`Suggestion`](https://github.com/nushell/reedline/blob/a4bfaa512be8b7214b80c63327930155da86978a/src/completion/base.rs#L58).
But I couldn't make it
- tried to use the `title` in the `value`, like this below, but when you
select a row, it pastes the title into the cli, so `gh pr checkout
<title>` doesn't make sense

![image](https://github.com/nushell/nu_scripts/assets/30557287/1c5caf7c-4653-49ba-afc2-ec8ba155b00f)



So, selecting the pr number is the closest I can get to
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants