tramlinehq/tramline

Backmerge commits onto upcoming release

Open

#648 opened on Sep 18, 2024

View on GitHub
 (0 comments) (0 reactions) (1 assignee)Ruby (32 forks)github user discovery
help wanted

Repository metrics

Stars
 (399 stars)
PR merge metrics
 (PR metrics pending)

Description

We currently have a missing link in Almost Trunk, where we should from merge commits when they land on the ongoing release onto an upcoming release as well, if there is one running. This is because the merges happen on the working branch only and not on the next release branch. We'd want the new release branch to be updated as well with new fixes.

Contributor guide

Research direction
Examine the existing Almost Trunk logic and identify where to add backmerge functionality for upcoming release branches.
Tech stack
ruby
Domain
releasedevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitRuby
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45