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.

Sign up for GitHub

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

Jump to bottom

fix(custom-search): revert underscore as quoted #8163

Merged
merged 1 commit into from Jun 16, 2023
Merged

fix(custom-search): revert underscore as quoted #8163

merged 1 commit into from Jun 16, 2023

Conversation

david-leifker
Copy link
Collaborator

Checklist

  • The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
  • Links to related issues (if applicable)
  • Tests for the changes have been added/updated (if applicable)
  • Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
  • For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@github-actions github-actions bot added the devops PR or Issue related to DataHub backend & deployment label Jun 2, 2023
@david-leifker david-leifker merged commit a5ee1ca into master Jun 16, 2023
33 checks passed
@david-leifker david-leifker deleted the david-leifker-patch-1 branch June 16, 2023 22:26
tusharm pushed a commit to tusharm/datahub that referenced this pull request Jun 20, 2023
@david-leifker @tusharm
fix(custom-search): revert underscore as quoted (datahub-project#8163)
ef4b055
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@RyanHolstien RyanHolstien RyanHolstien approved these changes

@iprentic iprentic Awaiting requested review from iprentic

Assignees
No one assigned
Labels
devops PR or Issue related to DataHub backend & deployment
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@david-leifker @RyanHolstien