Skip to content

Ticket change over#63

Draft
armanddidierjean wants to merge 2 commits intodevfrom
tickets-change-over
Draft

Ticket change over#63
armanddidierjean wants to merge 2 commits intodevfrom
tickets-change-over

Conversation

@armanddidierjean
Copy link
Copy Markdown

@armanddidierjean armanddidierjean commented Apr 8, 2026

Description

Summary

Requires aeecleclair/CalypSSO#193
...

Issues/PR dependencies

Issues to be resolved

Required PRs

Changes Made

  • ...
  • ...

Additional Notes

Classification

Type of Change

  • 🐛 Bug fix (non-breaking change which fixes an issue)
  • ✨ New feature (non-breaking change which adds functionality)
  • 🔨 Refactor (non-breaking change that neither fixes a bug nor adds a feature)
  • 🔧 Infra CI/CD (changes to configs of workflows)
  • 💥 BREAKING CHANGE (fix or feature that require a new minimal version of the front-end)
  • 😶‍🌫️ No impact for the end-users

Impact & Scope

  • Core functionality changes
  • Single module changes
  • Multiple modules changes
  • Database migrations required
  • Other: ...

Testing

  • 1. Tested this locally
  • 2. Added/modified tests that pass the CI (or tested in a downstream fork)
  • 3. Tested in a deployed pre-prod
  • 0. Untestable (exceptionally), will be tested in prod directly

Documentation

  • Updated the docs accordingly :
  • " Docstrings
  • # Inline comments
  • No documentation needed

@Rotheem Rotheem force-pushed the tickets-change-over branch from 9380cfc to 1bd4888 Compare April 8, 2026 19:17
@armanddidierjean armanddidierjean force-pushed the tickets branch 2 times, most recently from 9f25325 to cbae342 Compare April 16, 2026 19:59
Base automatically changed from tickets to dev April 19, 2026 21:34
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.

1 participant