Skip to content

feat: add reasons to exposure report object #929

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

Merged
merged 1 commit into from
Apr 4, 2025

Conversation

schaoukicoveo
Copy link
Contributor

@schaoukicoveo schaoukicoveo commented Apr 3, 2025

Acceptance Criteria

  • My changes are publicly available, documented, and deployed in production. (i.e. on Swagger)
  • JSDoc annotates each property added in the exported interfaces
  • The proposed changes are covered by unit tests
  • Commits containing breaking changes a properly identified as such
  • README.md is adjusted to reflect the proposed changes (if relevant)
  • My merge commit message will be conventional (See Conventional Commit)

@schaoukicoveo schaoukicoveo enabled auto-merge April 3, 2025 19:02
@schaoukicoveo schaoukicoveo added this pull request to the merge queue Apr 4, 2025
Merged via the queue into master with commit 025cb57 Apr 4, 2025
7 checks passed
@schaoukicoveo schaoukicoveo deleted the feature/ORG-1041 branch April 4, 2025 20:55
Copy link

github-actions bot commented Apr 4, 2025

🎉 This PR is included in version 58.17.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants