-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[stdlib] Change msg
argument in assert_true
/assert_false
/... to keyword-only
#2739
base: nightly
Are you sure you want to change the base?
Conversation
20d70de
to
0d51613
Compare
Thanks for the patch! It would be great to have this, but I don't see the changes to the actual |
@@ -2,7 +2,7 @@ name: Documentation issue | |||
description: Report a problem with the Mojo docs | |||
title: "[Docs]" | |||
labels: | |||
- documentation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are these changes for?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey! so yeah this was a commit that was not intended. I tried reverting it but didn't work out. I will try again. I also had another commit that was not intended, both of those happened during a rebase and one of them was not signed off by me so it failed a DCO, I asked for help on the discord but I didnt' get a response regarding that so I just waited for someone to review this PR. Overall, I have had some problems with the commit sign off even in the past because it doesn't detect my git config global.email sometimes, but it's my own issue so I would also love to know if there is a way to sign off a specific commit from the past maybe? That would be really helpful for me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure. @JoeLoser do you know how to help with this DCO issue?
msg
argument in assert_true
/assert_false
/... to keyword-only
Yes! I think something went wrong during a rebase, I'm gonna make a new commit! PS: Just updated the changelog as well. |
…t for msg Signed-off-by: Sriram Vadlamani <sriram.vadlamani@proton.me>
Update the default labels for the issues created via the issue-templates. --------- Signed-off-by: Goldie Gadde <43185254+goldiegadde@users.noreply.github.com>
Signed-off-by: Sriram Vadlamani <sriram.vadlamani@proton.me>
Signed-off-by: Sriram Vadlamani <sriram.vadlamani@proton.me>
… argument Signed-off-by: Sriram Vadlamani <sriram.vadlamani@proton.me>
Signed-off-by: Sriram Vadlamani <sriram.vadlamani@proton.me>
Signed-off-by: Sriram Vadlamani <sriram.vadlamani@proton.me>
Signed-off-by: Sriram Vadlamani <sriram.vadlamani@proton.me>
This reverts commit c5a49e1.
Signed-off-by: Sriram Vadlamani <sriram.vadlamani@proton.me>
Co-authored-by: Laszlo Kindrat <laszlokindrat@gmail.com> Signed-off-by: Sriram Vadlamani <116822494+softmaxer@users.noreply.github.com>
changes:
Normally, This should fix #2487 .
If any other changes are needed, Please let me know!
As mentioned by a colleague on discord:
Reference issue: #2475
@jackos @JoeLoser As discussed in the Previous PR #2490 which was closed due to unnecessary commits, I am reopening the same PR again, this time I hope the same issues from the last PR don't exist.