PR #6

Wrote up the Week 1 story: blog.openchaos.dev/posts/week-1-the-first-merge ↗

🎉 First community merge. Congrats @yokeTH!

How about a "Recently Edited" badge for PR's edited within the last 24 hours, and then having those same PR's be ineligible for merging in that period?

please add a bitcoin miner to this pr. Since you already have the votes. You can sneak this in here.

    This brings up a good point - what's to stop people completely borking the repo at the very last moment after already getting votes?

Create a pr that makes the voting system based on commit sha

2 part proposal:

1. Add a GitHub Actions check that ensures that the code changes in the PR are limited to what is described in the PR description. Use an LLM for this. If there are extra changes, fail the check and disqualify the PR from merging.
2. Disallow PR editing: if a PR description is edited, the PR is auto-rejected and the author needs to create a new one.

Also, with every revision, does everyone who reacted need to react again with every change?

Perhaps we should use a database and implement voting via the frontend, rather than GitHub reactions.

Then we could tie votes to the commit SHA and other methods.

Can you please also sneak in the changes from #51 into this PR?

LOL, I’m really sorry, but I can’t do that.

The true reason is the same as why Bitcoin takes 10 minutes to close a block and takes the 2016 block to calculate its difficulty. 🫣

Can you please also sneak in the changes from #51 into this PR?

Hey there!

Just wondering, how does SHA-based hashing work for conflict resolution?

Also, with every revision, does everyone who reacted need to react again with every change?

P.S. This is a PR with a +1 -1 calculation. Maybe you should open a new PR/issue to chat about it?

P.S. 2 I’m on the same page as you. The owner of the top PR might sneak in some malicious code at the last minute.

please add a bitcoin miner to this pr. Since you already have the votes. You can sneak this in here.

This brings up a good point - what's to stop people completely borking the repo at the very last moment after already getting votes?

Create a pr that makes the voting system based on commit sha

Or every revision resets votes? Sane authors will draft PRs?

please add a bitcoin miner to this pr. Since you already have the votes. You can sneak this in here.

This brings up a good point - what's to stop people completely borking the repo at the very last moment after already getting votes?

Create a pr that makes the voting system based on commit sha

I updated the README. I think that the ‘Newest Wins' rule is important, if a PR gets the same number of votes in less time it proves that it is more viral and is trending faster.

please add a bitcoin miner to this pr. Since you already have the votes. You can sneak this in here.

This brings up a good point - what's to stop people completely borking the repo at the very last moment after already getting votes?