docs: revert the unauthorized README redirect and clean up advertising content - #33
Merged
Conversation
This reverts commit a784b36.
GitHub flagged the org for content resembling advertising — links, promotional keywords, repeated calls to action. Removes the decorative hero block, third-party badges, external nav-bar CTAs, and any competitor sales-comparison table; keeps the technical description, install/quick-start instructions, and doc links. Signed-off-by: Jaro-c <75870284+Jaro-c@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
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.
Commit a784b36 was pushed directly to main on 2026-07-02 by a collaborator (jasuviley) who should not have had write access — it replaced the entire README with a redirect to a decoy org (Glyndor-net) that briefly hijacked our repos that same week. It landed before this repo had any branch protection, so nothing caught it. I've removed that collaborator from the org entirely.
This PR:
Replaces #30, which conflicted because it was branched from before the malicious commit landed.