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

[KBK-1] Resolve exception raised by user with no associated enrollment value #66

Merged
merged 1 commit into from
Oct 10, 2023
Merged

[KBK-1] Resolve exception raised by user with no associated enrollment value #66

merged 1 commit into from
Oct 10, 2023

Conversation

aethant
Copy link
Contributor

@aethant aethant commented Oct 10, 2023

Merge checklist:
Check off if complete or not applicable:

  • Version bumped
  • Changelog record added
  • Documentation updated (not only docstrings)
  • Fixup commits are squashed away
  • Unit tests added/updated
  • Manual testing instructions provided
  • Noted any: Concerns, dependencies, migration issues, deadlines, tickets

@aethant aethant changed the title feat: resolve exception raised by user with no associated enrollment value [KBK-1] Resolve exception raised by user with no associated enrollment value Oct 10, 2023
@aethant aethant requested review from ashultz0 and schenedx October 10, 2023 19:26
@aethant aethant merged commit a151e48 into main Oct 10, 2023
@aethant aethant deleted the KBK-1_1-ResolveException branch October 10, 2023 19:36
schenedx
schenedx reviewed Oct 10, 2023
View reviewed changes
Copy link
Member

@schenedx schenedx left a comment

Choose a reason for hiding this comment

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

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@schenedx schenedx schenedx left review comments

@ashultz0 ashultz0 ashultz0 approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@aethant @ashultz0 @schenedx