Angular

266 readers

2 users here now

A community for discussion about angular

Wormhole

!godot@programming.dev

Logo base by Angular under CC BY 4.0 with modifications to add a gradient and drop shadow

founded 1 year ago

MODERATORS

Ategon@programming.dev

fabian@programming.dev

Out of sync branches in a Angular Workspace (programming.dev)

submitted 1 year ago by magbeat@programming.dev to c/angular@programming.dev

2 comments fedilink hide all child comments

Hi there

I have a question about Angular workspaces:

We sometimes have long living branches next to develop. Now, if a team runs the schematics migrations from a library and update their code, it's possible that a different team (on a different branch) has new features that aren't updated by the schematics (because the new feature code obviously is not there).

Has anyone already had the same problem and found a solution?

top 2 comments

sorted by: hot top controversial new old

[–] muhanga@programming.dev 2 points 1 year ago (1 children)

I don't think that this is Angular specific. Long lived branches is a known problem in development world. So far I only encountered one solution/rule that worked (for me): long lived branches can only do nonbreaking changes. If you want to have a long lived branches and it will have a breaking change/feature, then you should first extract breaking behaviour to the develop branch and only then work in the long lived branch or feature.

This is obviously quite hard to do in some cases, but I didn't found anything else that works in such situations.

[–] magbeat@programming.dev 1 points 1 year ago

Yes, you are right. Long living branches are the problem.

In this case it is a completely new project in the workspace (of course depends on the library in the workspace). It is a POC that has been postponed again and again by the customer due to priorities.

I think it's probably best to isolate the branch and take it out of the workspace. When it is ready, we can integrate it back into the workspace.