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: Fix typo 'poisoning' in comments #1192

Merged
merged 2 commits into from
May 20, 2024
Merged

chore: Fix typo 'poisoning' in comments #1192

merged 2 commits into from
May 20, 2024

Conversation

pzrq
Copy link
Contributor

@pzrq pzrq commented May 17, 2024

Description

Related Issue

This is for a typo, so I disagree with a related issue being required (plus GitHub uses issues and pull requests interchangeably!), though I will create an issue if advised to do so.

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • [ ] Bug fix (non-breaking change which fixes an issue)
  • [ ] New feature (non-breaking change which adds functionality)
  • [ ] Breaking change (fix or feature that would cause existing functionality to change)
  • 4. chore

Checklist:

  • I have signed the Adobe Open Source CLA.
  • My code follows the code style of this project.
  • [ ] N/A My change requires a change to the documentation.
  • [ ] N/A I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • [ ] N/A I have added tests to cover my changes.
  • [ ] N/A All new and existing tests passed.

@krystiannowak krystiannowak self-requested a review May 20, 2024 10:34
@krystiannowak krystiannowak merged commit 2f23af5 into adobe:develop May 20, 2024
10 checks passed
@krystiannowak
Copy link
Collaborator

Thanks @pzrq !

@pzrq pzrq deleted the typo branch May 20, 2024 22:45
@rajatofficial rajatofficial added this to the 50 milestone Aug 13, 2024
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