feat(stacks): rework pages + new Jekyll tag - #3812
Merged
Merged
Conversation
EtienneM
approved these changes
Jul 31, 2026
EtienneM
left a comment
EtienneM
left a comment
Member
There was a problem hiding this comment.
Sorry I missed your request for comments on this PR
A bunch of questions and suggestions but already approving
Member
There was a problem hiding this comment.
I like it! It displays nicely and makes it clear the status of the mentioned stack
Frzk
marked this pull request as ready for review
August 20, 2026 07:48
EtienneM
approved these changes
Aug 21, 2026
EtienneM
left a comment
EtienneM
left a comment
Member
There was a problem hiding this comment.
I really love this change, thanks! 😍
…ack.md Co-authored-by: Étienne M. <EtienneM@users.noreply.github.com>
Co-authored-by: Étienne M. <EtienneM@users.noreply.github.com>
…ack.md Co-authored-by: Étienne M. <EtienneM@users.noreply.github.com>
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.
During the work related to the release of scalingo-26 and deprecation of scalingo-22, we noticed with @benjaminach that it was sometimes "hard" to understand what exactly lies behind "supported", "deprecated" and "discontinued".
This PR aims at making this clear by:
Tag usage (notice no
-betweenscalingoand the number!):