fix: Correct scripts/get.sh for ambiguous file extension - #6300
Benjamin-Loison wants to merge 1 commit into
Conversation
a91bc32 to
049a6a5
Compare
scripts/get.sh for ambiguois file extensionscripts/get.sh for ambiguous file extension
|
Thanks @Benjamin-Loison for your contribution :) |
049a6a5 to
ee8e025
Compare
|
@Benjamin-Loison Could you push signed commits? |
|
I am working on it @remyleone. My commit is signed, but not at GitHub taste, I am investigating at Benjamin_Loison/Improve_websites_thanks_to_open_source/issues/4138. |
Head branch was pushed to by a user without write access
ee8e025 to
f803935
Compare
|
@remyleone it should be good now. |
f803935 to
1202b76
Compare
|
Nope, still not verified dixit github. |
|
So, we've got more people raising issues about this on multiple channels, so I've cherry-picked your commit and signed it as committer, which github will allow. This should give you attribution correctly (of the commit if not the MR). |
|
Thank you for paying attention to attribution. I forgot to Personal notes: Benjamin_Loison/git/issues/153 |
Community Note
Closes #6299
I tested successfully update and install thanks to my changes.
Until this pull request is merged, a workaround is:
curl -s https://raw.githubusercontent.com/Benjamin-Loison/scaleway-cli/049a6a50838f40ba08f2c48cfa21f223cf89c066/scripts/get.sh | sh