Skip to content
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

chore: revert of #498 and #504 #511

Merged
merged 1 commit into from
Sep 22, 2022
Merged

chore: revert of #498 and #504 #511

merged 1 commit into from
Sep 22, 2022

Conversation

edyesed
Copy link
Contributor

@edyesed edyesed commented Sep 22, 2022

Background

double-checking #508 . This PR reverts #498 and #504 by selectively checking out the files updated in #498 from git hash 5e9165b. This hash was the most-recent hash on the primary branch before #498 merged.

Changes

Testing

  • make test

@edyesed edyesed requested review from a team September 22, 2022 21:51
Copy link
Contributor

@darwayne darwayne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this mean the other PR can be closed?

@edyesed
Copy link
Contributor Author

edyesed commented Sep 22, 2022

Does this mean the other PR can be closed?

yep, you're bit faster than I 😸 . I closed #510 without merge. If we're going to use this PR, #511, we should also close #508 without merging.

@rmarathay-zz
Copy link
Contributor

This looks good. (I'll close my PR)

@edyesed edyesed changed the title chore: double-check revert of 498 and 504 , this time against the master branch chore: revert of #498 and #504 Sep 22, 2022
@edyesed edyesed merged commit 2554e95 into master Sep 22, 2022
@edyesed edyesed deleted the fix/edyesed/check_508 branch September 22, 2022 22:29
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.

3 participants