-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Add Stephanie Bodoff to AUTHORS #69881
Conversation
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.
Hi Stephanie. Can you merge your commits into a single commit and then force-push to the branch? This will make it so the PR will follow our philosophy for how we write commits.
I'm used to squashing multiple commits into a single commit in the merge itself. I don't know how to do what you are asking. Could you help me with the procedure. |
Nevermind. The docs team has instructions for this. I'll apply those. |
Apologies for not including info on how to fix this earlier. Here's how to fix it:
|
Release note: None Release justification: Non-production code change
@jlinder I believe this is fixed now. |
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.
Indeed!
Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @stbof)
bors r+ |
Build succeeded: |
Release note: None