git Timeline - FediScanner

16.11.2025 21:21
GLubrano (@GLubrano@mastodon.uno)

Git: Passare ad un branch esistente

https://giovannilubrano.blogspot.com/2025/11/git-passare-ad-un-branch-esistente.html

16.11.2025 18:02
xolatgames (@xolatgames@mastodon.gamedev.place)

Hi, folks! ✌️ How are you? 🙃 So, I'm still here.

I decided to add a main menu to Vasya who go to (his) Home 🏡, and resume working on the next three levels for the second world 🏗️... And...

Here it is! 🥳 So, you can download this update from the Vasya's Codeberg page 🏔️, and play this 👉 https://codeberg.org/xolatgames/Vasya-go-to-home/releases/tag/v0.2.0

And that's all! See you later 😉

#rust #rustlang #git #codeberg #opensource #cargo #macroquad #appimage #game #games #gamedev #indie #indiedev #indiegame #inkscape #maze #actionAdventure

Show Original Post

Report

16.11.2025 17:46
NigelGreenway (@NigelGreenway@mastodon.social)

With a recent discovery of #git worktree's, I decided to write a #tmux plugin to manage/create worktrees with the added extra of creating a branch for that worktree

https://github.com/NigelGreenway/tmux-git-worktree

#foss #opensource

Show Original Post

Report

16.11.2025 15:40
hn50 (@hn50@social.lansky.name)

An exposed .git folder let us dox a phishing campaign

Discussion: https://news.ycombinator.com/item?id=45943802

#git

Show Original Post

Report

16.11.2025 15:24
vincentvdk (@vincentvdk@hachyderm.io)

I've been enjoying @Codeberg to manage my repositories. It's not overly filled with features but has just enough of what you would need from a Git repo. Still need to look further into the CI part but that also looks and is based on the #opensource @WoodpeckerCI #git

I'm planning on hosting more exising and new stuff over there. Follow me if you are interested

https://codeberg.org/vincentvdk

Show Original Post

Report

16.11.2025 14:59
masukomi (@masukomi@connectified.com)

#git nerds:
I want to store a file with metadata about the files I'm working on, BUT I want it to be invisible.

I'm thinking of using a post-commit hook that stores/updates/whatever this metadata file in a different - specially named - branch behind the scenes (without affecting the working directory).

BUT Something's telling me there's a better solution that I've forgotten. This feels clunky.

Any ideas?

Show Original Post

Report

16.11.2025 14:10
musicmatze (@musicmatze@social.linux.pizza)

I just did a thing: https://github.com/matthiasbeyer/git-forge-merge/

#git #github #codeberg #forgejo #softwaredevelopment