CI: ne pas interrompre track-en-changes si une création d'issue échoue#2908
Merged
Conversation
lacatoire
force-pushed
the
ci/track-en-resilient
branch
from
72729ec to
c42837f
Compare
Une erreur transitoire de l'API (401/5xx) sur un commit stoppait tout le run (set -e) et laissait de côté les commits restants. Chaque appel par commit (métadonnées, déduplication, création) tolère désormais un échec : le commit concerné est sauté et repris au run suivant (fenêtre 7 jours + dédup SHA), les autres sont traités. La création passe par un POST REST unique (gh api) pour éviter le pré-fetch de label qui avait renvoyé le 401. Les échecs persistants restent signalés (exit 1).
lacatoire
force-pushed
the
ci/track-en-resilient
branch
from
c42837f to
f10c8b3
Compare
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
1 participant
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.
No description provided.