Ecdar / Ecdar/j-Ecdar

Shorten lifetime of branches

Open
#75 1 comment 0 reactions 0 assignees View on GitHub
documentation
Dominant language
Java
Stars
4
Forks
9
PR merge metrics
No merged PRs in 30d

Description

I notice that current devolpment of different issues are merged into `new-cdd-function`. Yet, this branch is 136 commits ahead of our `main` branch. Imho this is bad, as currently `main` cannot used as a base for further development.

So my two suggestions are

1. Figure out when we will merge `new-cdd-function` into `main`, so that future development can actually be based upon `main`.
2. In the future we should limit the lifetime of our branches to prevent this issue from happening again. We could, for example, say that branches (and subsequent pull requests) should be single issue only, but other rules are also possible.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the history and relationship between `new-cdd-function` and `main`, then read the issue discussion for context on the proposed branch-lifetime problem. Done means the project has an agreed plan for merging the long-lived branch and a documented, accepted rule for future branches and pull requests.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, github
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.