Skip to content

Conversation

@sebastiantorrescodes
Copy link

Types of changes

  • Hot fix (emergency fix and release)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Documentation (change which affects the documentation site)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Release (develop -> main)

Quality assurance (all should be covered).

  • [ X] My code follows the code style of this project.
  • [ X] Documentation for my change is up to date?
  • [ X] My PR meets testing requirements.
  • [ X] All new and existing tests passed.
  • [ X] All commits are signed-off.

Summary

Key links:

Before you merge

  • Ensure it is a 'squash commit' if not a release.
  • Ensure CI is currently passing
  • Check sonar. If you are working for a fork a maintainer will reach out, if required.

@sebastiantorrescodes sebastiantorrescodes requested a review from a team as a code owner November 26, 2025 16:57
@degenaro
Copy link
Collaborator

Hi @sebastiantorrescodes I enabled the pipelines and they passed. However DCO is failing. See the slack channel for some info on signing. Also, @1aur was successful at signing - perhaps she can share with you.

@degenaro
Copy link
Collaborator

degenaro commented Dec 2, 2025

@sebastiantorrescodes Do you want to meet on Teams to move this PR forward? Soon or once semester ends?

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