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 syncstdout by @muzimuzhi in Quote repo names consistently ingh repo syncstdoutΒ #9491Internalfromgh repo createprompt when owner is not an org by @jtmcg in RemoveInternalfromgh repo createprompt when owner is not an orgΒ #9465gh run viewby @benebsiny in fix the trimming of log filenames forgh run viewΒ #9482repo syncby @muzimuzhi in Fix doc typo forrepo syncΒ #9509gh attestation verifyhandles empty JSONL files by @malancas ingh attestation verifyhandles 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