Lemmy Today

1,477 readers
89 users here now

Welcome to lemmy.today!

About us

🤗 Thanks for joining our little instance here, located in Oregon. The idea is to have a fast, stable instance and allow users to subscribe to whatever content they want from here.

😎 We dont block any other instances. We will keep it that way unless it becomes a moderation problem.

🤠 We will be around for a very long time, so you dont have to worry about us shutting down the instance anytime soon. We like performance and stability in our servers, and will upgrade the instance when its needed.

🥹 Make sure to join a lot of remote communities to get a good feed going. How to do that is explained here.

Lemmy mobile apps

You should start using one of these ASAP since the web browser user interface is quite ugly, even with themes.

Optional Lemmy web browser user interfaces

Rules

Contact the admin

founded 1 year ago
ADMINS
mrmanager
Buelldozer
listing: all - local
search
1
12
[HN] Gitlab's plan to support ActivityPub for merge requests (gitlab.com)
 
 

[ comments | sourced from HackerNews ]

2
303
GitLab plans support for ActivityPub (gitlab.com)
 
 

cross-posted from: https://lemmy.world/post/3802741

Several years in the making, GitLab is now very actively implementing ActivityPub! 🙌

The end-goal is to support AP for merge requests (aka pull requests), meaning git.alice.dev can send a merge request to gitlab.com/Bob/project.git

In the most expansive version of this vision, anyone running an AP-enabled git instance (with one or more repos) can send MRs to another instance’s repo, without having to sign up there.

For starters this will be GitLab-specific, but that’s already huge for self-hosters of GitLab who currently don’t benefit from the internal interop of the GitLab.com network.

First bite-sized todo on the implementation path there is ‘subscribe to project releases’. And yes, they are aware of ForgeFed and will likely make use of that spec for the advanced features of this epic.

Smart move by GitLab; through ActivityPub they’re getting a distributed version of GitHub’s social layer.

Hugely impactful as a way around GitHub’s moat as the de-facto social network of open source development. I follow hundreds of developers on GitHub, though mainly just to keep track of who I’ve interacted with, effectively adding them to a dev-specific address book.

I have a much harder time keeping track of non-GitHub devs on alt platforms, but if I could follow them on the fediverse that’s actually preferable over GitHub’s proprietary follow list.

Cross-posted to Mastodon: https://writing.exchange/@erlend/110949168258462158

3
667
GitLab plans support for ActivityPub (gitlab.com)
submitted 1 year ago* (last edited 1 year ago) by erlend_sh@lemmy.world to c/fediverse@lemmy.world
40 comments fedilink
 
 

Several years in the making, GitLab is now very actively implementing ActivityPub! 🙌

The end-goal is to support AP for merge requests (aka pull requests), meaning git.alice.dev can send a merge request to gitlab.com/Bob/project.git

In the most expansive version of this vision, anyone running an AP-enabled git instance (with one or more repos) can send MRs to another instance’s repo, without having to sign up there.

For starters this will be GitLab-specific, but that’s already huge for self-hosters of GitLab who currently don’t benefit from the internal interop of the GitLab.com network.

First bite-sized todo on the implementation path there is ‘subscribe to project releases’. And yes, they are aware of ForgeFed and will likely make use of that spec for the advanced features of this epic.

Smart move by GitLab; through ActivityPub they’re getting a distributed version of GitHub’s social layer.

Hugely impactful as a way around GitHub’s moat as the de-facto social network of open source development. I follow hundreds of developers on GitHub, though mainly just to keep track of who I’ve interacted with, effectively adding them to a dev-specific address book.

I have a much harder time keeping track of non-GitHub devs on alt platforms, but if I could follow them on the fediverse that’s actually preferable over GitHub’s proprietary follow list.

Cross-posted to Mastodon: https://writing.exchange/@erlend/110949168258462158

view more: next ›