Project

General

Profile

Actions
Copy link

Bug #21517

closed

Make rudder-dev aware of branches next for plugin

Added by François ARMAND over 2 years ago. Updated 6 months ago.

Status:
Released
Priority:
N/A
Assignee:
Benoît PECCATTE
Category:
Rudder dev tools
Target version:
master
Pull Request:
https://github.com/Normation/rudder-t...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:

Description

For plugin, the lifecycle is very complicated.
We have `7.1-next` that is the branch for rudder SNAPSHOT version.
Most dev happen in these branch.
Rudder dev does not know about them, so it tries to open PR or merge them in the standard `branches/rudder/7.1` branch.

Here, we want to at least provide a correct experience for:
- starting work on an issue (ie: rudder-dev 14345 should branch from origin/7.1-next if 14345 targets branche 7.1-next)
- commit
- merge by hand

Automatic merge may not work - it's ok, we don't want to keep that archi of branches on plugins.

Actions
Copy link

Also available in: Atom PDF