Skip to content

Conversation

@germanosin
Copy link
Member

  • Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)

Is there anything you'd like reviewers to focus on?

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

  • No need to
  • Manually (please, describe, if necessary)
  • Unit checks
  • Integration checks
  • Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
  • My changes generate no new warnings (e.g. Sonar is happy)
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged

Check out Contributing and Code of Conduct

A picture of a cute animal (not mandatory but encouraged)

@germanosin germanosin requested a review from a team as a code owner July 30, 2025 07:11
@kapybro kapybro bot added status/triage Issues pending maintainers triage type/feature A brand new feature status/triage/completed Automatic triage completed and removed status/triage Issues pending maintainers triage labels Jul 30, 2025
@Haarolean Haarolean added impact/documentation A PR with changes which should be addressed in the documentation type/chore Boring stuff, could be refactoring or tech debt and removed type/feature A brand new feature labels Aug 5, 2025
@Haarolean Haarolean changed the title Updated Feature List Docs: Updated feature list Aug 5, 2025
@Haarolean Haarolean merged commit 4656684 into main Aug 5, 2025
43 checks passed
@Haarolean Haarolean deleted the updated-features branch August 5, 2025 22:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

impact/documentation A PR with changes which should be addressed in the documentation status/triage/completed Automatic triage completed type/chore Boring stuff, could be refactoring or tech debt

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants