GitHub CLI 2.56.0 #9585
Replies: 5 comments · 4 replies
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
-
@andyfeller can/should release discussion posts be locked, or is the idea to have people file legit "issues"? Seems a number of spam comments are posted every single time (which I noticed when I'm mentioned). I don't recall seeing a legit comment, and shouldn't those be opened as issues instead? I appreciate that even then spam is possible, but it shuts down one obvious abuse of bots echo'ing a release note...which I don't understand how that's a thing? It's not even "spam" advertising something. 🤷♂️ |
Beta Was this translation helpful? Give feedback.
4 replies
This comment was marked as spam.
This comment was marked as spam.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
What's Changed
gh repo sync
stdout by @muzimuzhi in Quote repo names consistently ingh repo sync
stdout #9491Internal
fromgh repo create
prompt when owner is not an org by @jtmcg in RemoveInternal
fromgh repo create
prompt when owner is not an org #9465gh run view
by @benebsiny in fix the trimming of log filenames forgh run view
#9482repo sync
by @muzimuzhi in Fix doc typo forrepo sync
#9509gh attestation verify
handles empty JSONL files by @malancas ingh attestation verify
handles empty JSONL files #9541New Contributors
Full Changelog: v2.55.0...v2.56.0
This discussion was created from the release GitHub CLI 2.56.0.
Beta Was this translation helpful? Give feedback.
All reactions