🧮 Logik für Versions-Deployments aktualisiert #22
Conversation
This file contains 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
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.
đź“Ś Wichtige Ă„nderung im Release-Workflow
Mit dieser PR wird das System, wie neue Versionen entstehen, verändert.
❓ Was hat sich verändert?
Vorher war jedes Versionsupdate so aufgebaut, dass man alle Daten in den Branch
releaseverschieben musste. Das hat aber immer zu unangenehmen Nebeneffekten geführt. Deswegen wird jetzt jedes Versionsupdate mit einem Tag gekennzeichnet. Erstellt man einen, erstellt der Workflow den dazugehörigen Release automatisch.Wichtig zu beachten ist jedoch, dass dieser Tag immer mit einem v beginnen muss. Also z. B. v1.0.0 oder v1.2.0