Repository navigation
chore: keep the awesome-alternatives entry in .awesome-alternatives - #537
Merged
Merged
Conversation
BryanFRD
enabled auto-merge (squash)
October 6, 2026 12:07
Contributor
There was a problem hiding this comment.
Nothing blocking. The YAML is well formed, and the deploy values line up with what the repo ships (Dockerfile, chart/, packaging/). I didn't check the file against the remote schema or check the feature claims in the replaces notes against the server code.
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
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.
Closes #536
Replaces the one-line slug file with the maintainer file format from awesome-alternatives/awesome-alternatives#326. The values mirror the current catalog entry, so the next refresh changes nothing; later edits here are applied (facts) or proposed as a pull request (category, replacements, affiliation).