Fix jd4h multi server handling, updated readme and dependabot - #113
Merged
Merged
Conversation
gamingdy
requested review from
Alessevan,
AntoineJT and
Lindwen
as code owners
September 30, 2026 21:50
AntoineJT
previously approved these changes
Sep 30, 2026
AntoineJT
previously approved these changes
Sep 30, 2026
AntoineJT
approved these changes
Sep 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Correction d'un bug qui fait qu'on ne pouvait pas avoir le même utilisateur de jd4h sur différent serveur car seul la colonne user_id était en primary key, maintenant on a (user_id,guild_id)
Ajout d'une CI pour auto update le readme au niveau des contributeur et le dernier tag push ( oui c'est juste pour faire joli)
Ajout d'une regle dependabot comme ça il prévient que pour les petites maj de l'image python et arrête de demander de passer de 3.13 à 3.14
Une plus grosse maj du Readme est prévu, mais pour plus tard