Recent searches

No recent searches

Search options

Only available when logged in.
eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Administered by:

Server stats:

192
active users

eupolicy.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.1

#git

26 posts26 participants0 posts today
Digital Research Academy

New free online training announced: "Collaborative git without GitHub" by @petrichor 🧑‍💻

> Although git was created as a decentralised way to collaborate, the practical needs of day-to-day work have pushed most of us to use it through a centralised platform (generically called a “forge”), of which the most common is Microsoft’s GitHub.

📅 3 September 2025, 16:00 - 17:30 CET

More info and sign up:
events.digital-research.academ

DRA event platform (Indico) (Indico)Collaborative git without GitHubAlthough git was created as a decentralised way to collaborate, the practical needs of day-to-day work have pushed most of us to use it through a centralised platform (generically called a “forge”), of which the most common is Microsoft’s GitHub.Format Interactive online workshopAudienceThis workshop is for people who use GitHub to collaborate on code, writing or similar projects, and who would like to learn more about what alternatives are available. It’s especially aimed at researchers and...
#git#VersionControl
DocYeet :verified:

Help...

Does anyone around here know about tangled.sh/ ?
What would prevent me from using it as a mirror with my Forgejo instance while they implement Federations ?

I mean, it's on ATProto, not ActivityPub, so it would be replaced eventually...

Or maybe that's a more interesting solution for federating repositories altogether ?

What are your thoughts ?

(up @vilhelmbergsoe for showing me this great project)

#federated #forgejo #git #github #tangled.sh #tangled #activitypub #atproto #selfhosted #homelab #opensource #repository

tangled.shtimeline · tangledsee what's tangling
Replied in thread
*
Yann Büchau :nixos:

@blami @publicvoit :gitannex: #gitAnnex does this pretty well. It'll also keep all old versions of files in a read-only hidden directory tree until you tell or configure it otherwise and it'll stubbornly refuse to actually delete anything unless it can provably see there are N other copies elsewhere or you force it to. My synced files have never felt safer.

But its noob-UX is kinda terrible compared to :syncthing: #Syncthing - it's first and foremost a cli program: :git: #git

DrScriptt

I ran into a problem today where I needed to use different protocols / authentications methods / URLs for pulling (fetch) from and pushing to a #git repo.

It turns out that it's relatively straight forward to do:

--8<--
# git remote set-url --push ${REMOTE} ${URL}
-->8--

I was using a Deployment Key to for read-only pull (fetch) from a private GitHub repo, but I needed the ability to authenticate as myself to be allowed commit and push. -- Automation can pull (fetch) from the repo but is prevented from writing to it.

After changing the URL line in the .git/config file a few times, I searched and found that there is an easy way to have different protocols / authentication methods / URLs for pull (fetch) and push.

I thought that it might be the case, as I'd seen that `git remote -v` listed the same remote twice with the difference being `(fetch)` and `(pull)` on the two lines.

--8<--
# git remote -v
${REMOTE:-origin} ${URL} (fetch)
${REMOTE:-origin} ${URL} (push)
-->8--

Thorsten Leemhuis (acct. 1/4)

#Git 2.51 is out:

github.blog/open-source/git/hi

lore.kernel.org/all/xmqqikikk1

A few quotes from the former URL:

Cruft-free multi-pack indexes […] Using this at GitHub has allowed us to write significantly smaller MIDXs, in a fraction of the time, and resulting in faster repository read performance overall.

Smaller packs with path walk […] As a result, Git can generate packs using the path walk approach that are often significantly smaller

[…] Git 2.51 introduces a variant of the internal stash representation that allows multiple stash entries to be represented as a sequence of commits. […]

[…] git switch and git restore […] are no longer considered experimental […]

[…] git whatchanged […] is now marked as deprecated with eventual plans to remove it in Git 3.0. […]

Speaking of Git 3.0, this release saw a few more entries added to the BreakingChanges list (github.com/git/git/blob/v2.51. ). […]

[…] this release saw an update to Git’s guidelines on submitting patches, which have historically required contributions to be non-anonymous, and submitted under a contributor’s legal name. Git now aligns more closely with the Linux kernel’s approach, to permit submitting patches with an identity other than the contributor’s legal name. […]

The GitHub Blog · Highlights from Git 2.51The open source Git project just released Git 2.51. Here is GitHub’s look at some of the most interesting features and changes introduced since last time.
Johan Vervloet

I don't understand why #git is considered a tool for programmers. It should be used everywhere by people that need to edit documents.
(And let's get rid of office document formats, and all move over to #markdown! 💪)

TrendingLive feeds
About