News for hackers. Stuff that matters.

A comment on Critical Security Release for GitLab 8.2 through 8.7. Parent comment

Re:Critical Security Release for GitLab 8.2 through 8.7 by daxelrod on Tuesday May 03, 2016 @09:14AM (#11620280)
Since every project is isolated, how do you handle operations that require data from multiple projects, such as the activity feed or merge requests?

I'm also curious, how extensively do you need to modify GitLab for Sandstorm? Is that https://github.com/dwrensha/gitlab-sandstorm ?

[ Parent | on HN ]
Re:Critical Security Release for GitLab 8.2 through 8.7 by kentonv on Tuesday May 03, 2016 @02:04PM (#11622882)
> Since every project is isolated, how do you handle operations that require data from multiple projects, such as the activity feed or merge requests?

Right now: Poorly.

But in a few months: - We're adding an activity feed API to Sandstorm, so that you can get a unified feed and notifications across all apps. - The Powerbox (https://sandstorm.io/how-it-works#powerbox) allows connecting grains to each other. We will define a git API which each of the git apps (Gitlab, Gitweb, Gogs) can implement, so that you can even do cross-app merge requests.

[ Parent | on HN ]