Skip to content

Remove exploded variable #34938

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

Closed
wants to merge 21 commits into from
Closed

Remove exploded variable #34938

wants to merge 21 commits into from

Conversation

erfannariman
Copy link
Member

@erfannariman erfannariman commented Jun 22, 2020

@erfannariman
Copy link
Member Author

erfannariman commented Jun 22, 2020

@TomAugspurger would you mind to trigger a rerun here as well? Btw, I'm not sure why my commits of the other branch are shown here..

@erfannariman erfannariman changed the title Remove exploded variable #34934 Remove exploded variable Jun 23, 2020
@MarcoGorelli
Copy link
Member

Btw, I'm not sure why my commits of the other branch are shown here..

This is probably because you created this new branch from the other one. In general, I usually do

git checkout -b <new-pr-branch>
git fetch upstream master
git reset --hard upstream/master

before starting to work on a new PR to make sure this doesn't happen

would you mind to trigger a rerun here as well?

If you rebase onto upstream/master, drop the unrelated commits, and force push, it should re-run

@erfannariman
Copy link
Member Author

@MarcoGorelli I created a new PR, because this branche was messed up. I will close this one, see: #34949

@erfannariman erfannariman deleted the remove_exploded_variable_34934 branch June 23, 2020 12:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BUG: unnecessary repetition of variable in explode test
2 participants