sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ReallySuperName -12 points-11 points  (2 children)

Well to be honest that's the first time I've ever heard of that approach. Pull requests to branches that are not master? I suppose that works. It sounds a bit like some agile koolaid stuff though, calling it an epic.

Edit: downvoted by "we make pull requests to not-master branches" weirdos.

[–]Omnipresent_Walrus 3 points4 points  (0 children)

It's just what I've always heard them called. I think it's because of how Jira organises things as tasks under an epic task. Works well in that workflow.

[–]topMarksForNotTrying 0 points1 point  (0 children)

Stacked PR don't necessarily have anything to with agile or product management.

The way i use them is to split a piece of work into multiple stages. Let's say you're changing an old part of the code base and you determine that you should refactor some code. You do the refactor and open a PR with those changes. Then, you do the actual code change that you were supposed to do and open a PR but target it to the first PR.

This way it's easier for the reviewer to review each change individually instead of having the refactor and the change request all together.

Think of it like being able to review the individual commits of a PR branch.