shortly closing as I prefer 207

Closing because 13 was closed

The merged #185 is better and chaotic.

Was fixed at #130

Fixed now

Fixed now

I have no idea what happened here.

I've given up my try of injection of the rule. :smiley:

The auto merging PR is already depending on the implicit rule, I just explicitly described it. Currently, the upvote of this PR is just 11, so it is enough just to mention the added rule in the title of PR. (Lazy thinking, maybe)

I was wrong. Please save us from the void!

Please check the items in the Test plan section.

iirc, this requires a special setting in the project.

graph TD
    Start([The Beginning of OpenChaos])
    Start --> PR[Merge the Most Upvoted PR]

    PR --> Check{Is this the 1.337%<br/>Blank Page PR?}

    Check -- Yes --> Collapse[OpenChaos Collapses]
    Check -- No --> Wait[Wait 24 Hours]
    Wait --> Start

This did not work for OpenChaos Bot somehow

The real problem I am facing is the browser I am using is Firefox Mobile, and it does not support a respective reflow zoom setting per site.

Please Indicate when you are being a naughty boy.

🤦

I can't wait for this anymore

Think this could use an epileptic mode. When the user switches light/dark mode, at random prompt the user as to whether or not they're epileptic and if they say no rapidly switch between light an dark mode for a few seconds. Thoughts?

That sounds like malicious software. Wait, isn't 'malware' the abbreviation for that? According to our rules, malware must be rejected and should not be merged.

Okay I've set the indentStyle to two spaces and quoteStyle to single

Why sort=updated here?

Folks, you don't need to get too invested. I genuinely laughed out loud watching @matthewmayer encourage dickbutt PR, and I'm also enjoying @skridlevsky 's summaries on the blog. I don't think this repository needs to be a propaganda platform for democracy, nor was there any indication it would be. Not every vote is necessarily democratic, and where was it ever stated that this vote needed to be democratic? Anyway, I'm just enjoying watching this funny and entertaining situation unfold. (machine translated)

Not merging this PR. @marcaddeo caught hidden code that manipulates the ranking - PRs by @FelixLttks sort to top regardless of votes, plus a featured visual style. The health indicator feature is legit and welcome. The sorting/styling manipulation is not. This falls under "No malware: Maintainer can reject obviously malicious content." Remove the btoa hacks and this ships. Until then, skipping to next eligible PR.

This feels like an overreach. Is altering business logic really malware?

We should describe the meaning of "malicious" in detail by a PR. Before done it, it depends on how @skridlevsky think.

Regardless of your heated discussions, I wanted to share the news that GeoCities PR has been merged, and the site has truly transformed beautifully. https://www.openchaos.dev/ ↗ ​It is beautiful not only on the outside but also on the inside, with a mix of Tailwind, inline styles, and raw CSS.

lgtm

I like this idea. If we do not urgently prevent the last-minute bait-and-switch commits, someone(maybe I) would change the whole contents of openchaos.dev with a sign saying "The OpenChaos project is over".

Don't worry too much. That PR doesn't go as far as changing the merge cycle defined in the rules back to a week. Even if all existing PRs fail the CI, maintainers will still merge new ones that pass according to the rules, so we can fix things then.

The music is really charming and relaxing. Thank you!!!

This PR looks most likely to be merged next. Good job!

This needs an update to only merge PRs that are passing checks. Otherwise the system will completely break.

I mean you only have to check the commit I mentioned contains only the results of npm run format -- --fix. Maybe it can be done

gh pr checkout 106
git reset --hard @^
npm i
npm run -- --format
git diff 6e3d782 @      # I am not sure

It was my fault in English.

Oh, you accidentally clicked downvoted. But it is okay because the huge changes only done in 6e3d782 and it is auto-generated by npm run format -- --fix so you only have to verify whether I lie or not.

🥲

Biome

https://biomejs.dev/ ↗

Biome is a fast formatter for JavaScript, TypeScript, JSX, TSX, JSON, HTML, CSS and GraphQL that scores 97% compatibility with Prettier ↗, saving CI and developer time.

Lefthook

https://lefthook.dev ↗

Lefthook is a Git hooks manager

This is confusing, even if it is intended (idk!)

cc @bpottle

Now a PoC. I will rebase this before merging.

Makes sense. Thank you.

Does the maintainer have time to conduct security reviews?

I thought we wanted chaos?

In that case, the following line should be removed or reworded.

https://github.com/skridlevsky/openchaos/blob/e22bf27c9347b2fbdc31e030e4cf0e2dcbf4b94f/README.md?plain=1#L26

Perhaps the author wanted to say that rewriting everything in Rust is chaos and nonsense.

And the merge is done manually; while #63 may help with daily deployments, it could become risky again.

Does the maintainer have time to conduct security reviews?