Post AMZzgD7zuGz8dTZMsy by sjors@m.sprovoost.nl
(DIR) More posts by sjors@m.sprovoost.nl
(DIR) Post #AMZzgCdVjcbB6vJ1Mm by waxwing@x0f.org
2022-08-09T10:32:56Z
0 likes, 0 repeats
Turns out that *more* than one of the contributors to Joinmarket has had their github account banned/blocked, but it seems not directly related to current news - it seems it happened specifically to people that only logged in via Tor.I'm not sure of details, obviously, just reporting what I've heard.Gitlab migration may be incoming.#joinmarket #bitcoin #github
(DIR) Post #AMZzgD7zuGz8dTZMsy by sjors@m.sprovoost.nl
2022-08-11T19:02:01Z
0 likes, 0 repeats
@waxwing any updates on this?
(DIR) Post #AMZzgDXWNNOxudVkfY by waxwing@x0f.org
2022-08-11T19:05:26Z
0 likes, 0 repeats
@sjors yes. i have had reports that some are *not* having problems while logging in only over Tor. But obviously one cannot know all the personal details of each person (e.g. how/when did they create their account, what else have they done). So in the dark, which is as usual for such things ...
(DIR) Post #AMZzgDvyuQy38UxHnM by stevenroose@x0f.org
2022-08-16T08:14:53Z
1 likes, 0 repeats
@waxwing @sjors Considering a self-hosted #Gitea instance? They're quite close to being #ForgeFed federation-ready so you can contribute cross-instance.
(DIR) Post #AMag5Ygd5MiyoSXO4m by waxwing@x0f.org
2022-08-16T16:10:08Z
0 likes, 0 repeats
@stevenroose @sjors i was interested in this, but then somebody told me that you can only sync the repo to the self-hosted gitea not the issues/PRs?
(DIR) Post #AMeW9xBbiU3R2vK9C4 by stevenroose@x0f.org
2022-08-18T12:37:45Z
0 likes, 0 repeats
@waxwing @sjors Not sure what you mean with this..
(DIR) Post #AMf8TviyDJOOtYSl3g by waxwing@x0f.org
2022-08-18T19:47:07Z
0 likes, 0 repeats
@stevenroose @sjors I mean, obviously this is only needed for issues/PRs, not for code, right? In which case code-only replication is not interesting. I think I must have missed something.
(DIR) Post #AMfMdzx8kI1SGPmmJM by stevenroose@x0f.org
2022-08-18T22:25:50Z
0 likes, 0 repeats
@waxwing @sjors Like @raucao pointed out the migration procedure #Gitea provides you can migrate most GitHub data over to the new instance.And with federation, people from public instances like@codeberg@mastodon.technology can (will be able to*?) automatically contribute to repos on your instance without having to create an account locally.
(DIR) Post #AMuxHMQnkxl3JRBRgm by sjors@m.sprovoost.nl
2022-08-26T10:56:57Z
0 likes, 0 repeats
@stevenroose @waxwing @raucao > this is only needed for issues/PRs, not for code, rightIdeally you want a backup of every version of the pull request, at the time the comments were coming in. In Bitcoin Core those disappear because the commits in pull requests are kept clean using force pushes.
(DIR) Post #AMvJKypNebLEG0oM52 by raucao@kosmos.social
2022-08-26T14:31:24Z
0 likes, 0 repeats
@sjors @stevenroose @waxwing Force pushes are an antipattern and should be avoided. PRs need the full history for people to follow updates most efficiently. The branch should be cleaned up when (or just before) merging the code IMO. GitHub even has a button for squash-merging.
(DIR) Post #AMvJKzLHjyrVqxjpoG by stevenroose@x0f.org
2022-08-26T15:04:09Z
0 likes, 0 repeats
@raucao @sjors @waxwing yeah this squashing is what force pushes are for, right? Often during different stages in review, I think it can be useful to force-push into a clean history from time to time during a longer review process
(DIR) Post #AMvJL0JC9EmgqllgBs by raucao@kosmos.social
2022-08-26T14:33:28Z
0 likes, 0 repeats
@sjors @stevenroose @waxwing That said, code comments aren't directly tied to commits, and they are indeed migrated to GItea when using Gitea's built-in migration tool.
(DIR) Post #AMz3uXyQ9YS8lFoimm by sjors@m.sprovoost.nl
2022-08-28T10:30:07Z
0 likes, 0 repeats
@stevenroose @raucao @waxwing the three downsides of squash commits are:1. You lose the PGP sig of the original author2. Git blame provides less clear historical documentation, because the realchange is burried onder "fixup" instead of actual3. I tend to review PR per commit. Reasoning through bugs that are fixed in later commits is more difficult and error prone.Some devs keep unsquashed history in a seperate branch, but that involves more skill, i.e. barrier to contributing.