Ask HN: Automating Staging Branch

I've been thinking for about 5 years about how much dull actions is managing staging branch when you're developing a project.

Just imagine you have to do it every single day:

- merge each feature

- resolve conflicts

- repeat it after each release because you need to reset it to the master branch

- don't forget to merge all features again and resolve conflicts again

- you never know how actual staging branch is

I did try to solve this with local scripts but my boiling point reached a year ago when I got tired of all this questions in my team "can I reset the staging branch", "how actual it is" and so on.

And finally I've build a prototype and we're happy using it for half a year. Now, all we need to do to keep staging branch always actual is just add "staging" label to the pull request. The bot will always reassemble staging branch after new commits and releases from labeled pull requests. I'm wondering how useful this app will be for other teams. Will you introduce such workflow to your team?

Let's imagine it'll cost you $5/mo for 2 users with unlimited projects and $50/mo for unlimited users.

Is this a real issue or I'm just only one who seems concerned.