That looks like the PR from hell - 190 files changed, 143 commits? Mostly with names like "tidy" and "wip" Props to whoever actually reviewed that, you are a warrior
I prefer to read the unified diff and commits don't matter as much.
Bluesky migrates to single-tenant SQLite
31–40 of 247 posts
Re: Bluesky migrates to single-tenant SQLite
#32That looks like the PR from hell - 190 files changed, 143 commits? Mostly with names like "tidy" and "wip" Props to whoever actually reviewed that, you are a warrior
Re: Bluesky migrates to single-tenant SQLite
#33What do they mean by "Since SQLite does not support concurrent transactions" - it supports them, as long as you don't access the .db file through a file share (UNC, or NFS, etc) - https://www.sqlite.org/wal.html I've been using this to update/read db from multiple threads/processes on the same machine. You can also do snapshotting with the sqlite backup API, if you want consistent view, and to not hold on transaction…
Re: Bluesky migrates to single-tenant SQLite
#34That looks like the PR from hell - 190 files changed, 143 commits? Mostly with names like "tidy" and "wip" Props to whoever actually reviewed that, you are a warrior
I prefer to read the unified diff and commits don't matter as much.
Re: Bluesky migrates to single-tenant SQLite
#35That looks like the PR from hell - 190 files changed, 143 commits? Mostly with names like "tidy" and "wip" Props to whoever actually reviewed that, you are a warrior
I prefer to read the unified diff and commits don't matter as much.
Re: Bluesky migrates to single-tenant SQLite
#36Earlier quoted context omitted.
I prefer to read the unified diff and commits don't matter as much.
don't know why, but recent teams around me have always made strict rules about number of commits in PRs. I just wanted to tell them the same thing you said: "Why don't you just look at the diffs?" curious for other opinions. (sorry not really about this particular topic)
Re: Bluesky migrates to single-tenant SQLite
#37Earlier quoted context omitted.
I prefer to read the unified diff and commits don't matter as much.
Commit your code and commit it often. There's no reason not to.
If your PRs are tiny it's not a big deal, but with 190 files changed in this one, it absolutely should have been rebased into a more reasonable commit history.
Re: Bluesky migrates to single-tenant SQLite
#38Earlier quoted context omitted.
I prefer to read the unified diff and commits don't matter as much.
don't know why, but recent teams around me have always made strict rules about number of commits in PRs. I just wanted to tell them the same thing you said: "Why don't you just look at the diffs?" curious for other opinions. (sorry not really about this particular topic)