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

feature/fix_db_ser_element_null_reason #317

Merged
merged 3 commits into from Feb 4, 2022
Merged

feature/fix_db_ser_element_null_reason #317

merged 3 commits into from Feb 4, 2022

Conversation

stefanspiska
Copy link
Contributor

@stefanspiska stefanspiska commented Feb 3, 2022 •
edited

@stefanspiska
update CHANGELOG.md
3b4f8de 
see CDR-222
@stefanspiska stefanspiska marked this pull request as ready for review February 3, 2022 11:35
@sonarcloud
Copy link

sonarcloud bot commented Feb 4, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

100.0% 100.0% Coverage
0.0% 0.0% Duplication

@stefanspiska stefanspiska merged commit 0508b98 into develop Feb 4, 2022
@stefanspiska stefanspiska deleted the feature/fix_db_ser_element_null_reason branch February 4, 2022 15:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@subigre subigre subigre 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.

null_reason not getting committed
2 participants
@stefanspiska @subigre