#Tag
Je réalise que j'ai oublié de poster la vidéo de ma présentation au dernier #humantalks à #grenoble. Je parle de #git, plus précisément des #worktree, de #bisect et #revert.
Ça dure 6mn de live démo, et avec les questions on est à 12mn. Et merci @PacoVelobs pour le caméo !
#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?
What about plugins in GitRoot? They are essential. Without them, you just have #Git repositories; with them, you get a full-featured #forge.
Currently, plugins are #wasm binaries following the #wasi specification. They can read/write to your Git repository and web space (files in a directory).
They are triggered on every push diff, depending on your `.gitroot/plugins.yml` configuration. More on plugin rights: https://gitroot.dev/doc/how-tos/plugin_rights.html
1/3
What about plugins in GitRoot? They are essential. Without them, you just have #Git repositories; with them, you get a full-featured #forge.
Currently, plugins are #wasm binaries following the #wasi specification. They can read/write to your Git repository and web space (files in a directory).
They are triggered on every push diff, depending on your `.gitroot/plugins.yml` configuration. More on plugin rights: https://gitroot.dev/doc/how-tos/plugin_rights.html
1/3
Je réalise que j'ai oublié de poster la vidéo de ma présentation au dernier #humantalks à #grenoble. Je parle de #git, plus précisément des #worktree, de #bisect et #revert.
Ça dure 6mn de live démo, et avec les questions on est à 12mn. Et merci @PacoVelobs pour le caméo !
# "Using LibreOffice and other Free software for documents as a lawyer"
I was asked recently about how I get on using LibreOffice for document-related legal work, and I promised to write down some thoughts.
The short answer is that I use a mix of LibreOffice and other FOSS tools, and I’m very positive about it, with no particular concerns.
If you have questions, please do ask!
https://neilzone.co.uk/2025/11/using-libreoffice-and-other-free-software-for-documents-as-a-lawyer/
A feature that’s currently missing from @forgejo (and thus @Codeberg) is the ability to move issues between repositories (see https://codeberg.org/forgejo/forgejo/issues/1280).
Thankfully, Benjamin Melançon created Forego Helpers with a move_issue.py script that does this using the Forgejo API. Sadly, the script has a bug in it (a tiny regression introduced during a refactor) and their Forgejo instance doesn’t have signups so I couldn’t create a pull request, so here is a fork for the time being that you can use:
https://codeberg.org/aral/forgego-helpers
While fixing the bug, I also updated the project to use uv (https://docs.astral.sh/uv/) – think of it as a single tool that’s the equivalent of nvm and npm in Node.js that makes Python, well, usable out of the box.
So to move issue #299 from kitten/app to kitten/site on Codeberg, for example, you’d run the following in your terminal:
```shell
uv run move_issue.py kitten app 299 kitten site
```
That will move the issue (including comments), comment on both the old and new issues to link them together, and then close the old issue.
Enjoy!
#forgejo #codeberg #issues #repositories #git #movingIssues #python #uv #tools
🌀 ¡Miércoles, Git! Manejo de errores en #Git y no morir en el intento
Aprendé a resolver 7 errores comunes en Git y ganar confianza desde #RStats.
Con Maëlle Salmon y Yanina Bellini Saibene
📅 2 Dic, 10:00–12:00 (UTC-3) – Online
💵 Estudiantes USD 5 · Académicos USD 10 · Industria USD 15
🔗https://www.eventbrite.com.ar/e/1937068908249
Mergiraf: Syntax-Aware Merging for Git
https://lwn.net/SubscriberLink/1042355/434ad706cc594276/
#HackerNews #Mergiraf #Syntax-Aware #Merging #Git #VersionControl #DevTools #CodeMerge
Nice! Misschien nog goed om te melden dat Forgejo een hard fork is van Gitea en hoe het zich daartoe verhoudt qua organisatie en ontwikkelkracht (zie ook: https://forgejo.org/compare-to-gitea/). En is er ook gekeken naar wat andere buitenlandse overheden gebruiken en waar mogelijk samen op te trekken? Zo zag ik dat het Duitse https://opencode.de/ op Gitlab draait.
1/3
@pauldekkers
@Corneel
@quartje
@wsslmn
@joeldebruijn
Sorry, maar er komt nog meer #GIT-weekendliteratuur aan… ach, weekend, eigenlijk gewoon al voor in de midweek!!
Ik heb in blog met een aanbeveling voor de Git-werkplaats van de #overheid geschreven:
https://developer.overheid.nl/blog/2025/11/11/git-forge-overheid
Conclusie: vanuit het oogpunt van digitale soevereiniteit en digitale autonomie is een self-hosted #Forgejo de beste keuze voor de overheid.
#Git #DigitaleSoevereiniteit #DigitaleAutonomie #GitLab #GitHub #FOSS #OpenSource #GitForge #SelfHosting
There's all good news on the Dutch government front looking into using #FOSS alternatives for their own services and #OpenSource projects.
@janvlug just published a blog post (in Dutch) on how @developer is considering #Forgejo code forge, the #git forge software that #Codeberg host for more than 200k people, serving more than 300k repositories.
https://developer.overheid.nl/blog/2025/11/11/git-forge-overheid
Also follow @Gina updates on Dutch government plans, and participate in the discussions and polls. 💪
🚀 GitNex 11.0.0 is out!
This release brings a custom URL scheme for easier access to your own instances, plus new features and bug fixes.
✨ Highlights:
• Repository topics
• Add or delete topics
• View global repo settings as an instance admin
Release Notes: https://codeberg.org/gitnex/GitNex/releases
A space for Bonfire maintainers and contributors to communicate
