Pipeline subscriptions for private and team repos

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Release notes

Problem to solve

Upstream pipeline subscriptions are only possible for public upstream projects.

Making all upstream projects public isn't a valid solution for many companies

Intended users

• Delaney (Development Team Lead)

User experience goal

The user should be able to setup pipeline subscriptions on projects where they are at least a developer.

Proposal

Make Pipeline Subscriptions available for repositories where the user is at least a developer.

separate issue: And it will be nice if the pipeline subscriptions can be set via gitlab ci file too instead of setting the upstream pipeline subscriptions via the ui.

Permissions and Security

• Add expected impact to members with no access (0)
• Add expected impact to Guest (10) members
• Add expected impact to Reporter (20) members
• Add expected impact to Developer (30) members
• Add expected impact to Maintainer (40) members
• Add expected impact to Owner (50) members

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references