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

refactor: Refactoring key errors #100

Merged
merged 6 commits into from
Dec 15, 2023
Merged

Conversation

PritishBudhiraja
Copy link
Contributor

Type of Change

  • Bugfix
  • New feature
  • Enhancement
  • Refactoring
  • Dependency updates
  • Documentation
  • CI/CD

Description

Motivation and Context

How did you test it?

Checklist

  • I ran npm run re:build
  • I reviewed submitted code
  • I added unit tests for my changes where possible

@PritishBudhiraja PritishBudhiraja requested a review from a team as a code owner December 15, 2023 08:41
@github-actions github-actions bot added the S-conventions-not-followed Status: This PR does not follow contributing guidelines label Dec 15, 2023
@PritishBudhiraja PritishBudhiraja changed the title Refactoring key errors refactor: Refactoring key errors Dec 15, 2023
@github-actions github-actions bot removed the S-conventions-not-followed Status: This PR does not follow contributing guidelines label Dec 15, 2023
@PritishBudhiraja PritishBudhiraja self-assigned this Dec 15, 2023
@PritishBudhiraja PritishBudhiraja added the S-waiting-on-review Status: This PR has been implemented and needs to be reviewed label Dec 15, 2023
@PritishBudhiraja PritishBudhiraja added this pull request to the merge queue Dec 15, 2023
Merged via the queue into main with commit 1ddbe68 Dec 15, 2023
4 checks passed
@PritishBudhiraja PritishBudhiraja deleted the refactoring-key-errors branch December 26, 2023 12:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: This PR has been implemented and needs to be reviewed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants