Skip to content

ELI-406: no person_data, so error response#293

Merged
Karthikeyannhs merged 3 commits intomainfrom
feature/ELI-406_no_person_data_so_error_response
Aug 12, 2025
Merged

ELI-406: no person_data, so error response#293
Karthikeyannhs merged 3 commits intomainfrom
feature/ELI-406_no_person_data_so_error_response

Conversation

@Karthikeyannhs
Copy link
Copy Markdown
Contributor

@Karthikeyannhs Karthikeyannhs commented Aug 12, 2025

Description

Context

Type of changes

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I am familiar with the contributing guidelines
  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

@Karthikeyannhs Karthikeyannhs merged commit 5fb57a7 into main Aug 12, 2025
22 checks passed
@Karthikeyannhs Karthikeyannhs deleted the feature/ELI-406_no_person_data_so_error_response branch August 12, 2025 11:21
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.

2 participants