You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Figure out when we will merge new-cdd-function into main, so that future development can actually be based upon main.
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.
The text was updated successfully, but these errors were encountered:
The plan is to merge new-cdd-function into main when 74 is closed.
I agree on this. I personally think a branching strategy like Git Trunk is very good for its simplicity.
Also, I think this issue might highlight the need for a for a CONTRIBUTING.md and CODE_OF_CONDUCT.md
I notice that current devolpment of different issues are merged into
new-cdd-function
. Yet, this branch is 136 commits ahead of ourmain
branch. Imho this is bad, as currentlymain
cannot used as a base for further development.So my two suggestions are
new-cdd-function
intomain
, so that future development can actually be based uponmain
.The text was updated successfully, but these errors were encountered: