home.social

#codeberg — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #codeberg, aggregated by home.social.

  1. PSA: if you use don't click the merge button on pull requests. don't use the web interface to merge pull requests!

    codeberg.org/Codeberg/Communit

    current responses on that thread are giving the runaround; hopefully they will act on it. sometimes, when you click merge on pull requests on codeberg, the patches will actually not show up in your git history, even when the PR shows as merged. this happened to me twice recently.

    the second time i noticed it, and i was able to pull from my repo, and find the exact commit ID from the merged patch, but it wasn't on any branch. detached HEAD. so i checked out that commit ID, created a branch locally, and merged back into my master.

    for now, absent migration to another code hosting provider, i will download patches from PRs manually and merge them locally, before re-pushing.

    see issue. i hope they fix it. the current response there accuses me of force pushing - i didn't.

    was gonna stay quiet but that initial response there displeases me.

  2. @[email protected] @[email protected]

    #GitHub isn't the right location... #Tusky moved to #Codeberg.

    Latest release of Tusky is version 33.1 (October 2026).
    (Latest commit is just two days ago.)

    https://tusky.app/
    https://codeberg.org/tusky/Tusky/
    https://f-droid.org/de/packages/com.keylesspalace.tusky/

    Btw.: Derived from #Tusky is #Pachli, currently v3.10.0 (Oct. 2026).
    https://pachli.app/

Share on Mastodon

Enter the server where you have an account.