This is a Discussion
🎩 Description
master is too unstable to use it as a base for developing new features.
As the state of master is most of the time with tests failing, Pull Requests become very difficult to get right. It is becoming usual to take around 5 days to get a PR right.
Then if this PR is not quickly merged into master, automatic merging rapidly disappears and another round of manual mergings and modifications starts again.
What I would expect is that merging master never introduces non passing tests into my current branch.
I'm far from an expert with the organization of git repos with large teams but I think that we should try to solve this situation that is slowing down developments.
One thing that may be related with this issue is the fact that running tests is very slow. This makes feedback very slow.
/cc
@decidim/product @decidim/lot-core
📌 Related issues
- All issues are related with this one.
This is a Discussion
🎩 Description
masteris too unstable to use it as a base for developing new features.As the state of
masteris most of the time with tests failing, Pull Requests become very difficult to get right. It is becoming usual to take around 5 days to get a PR right.Then if this PR is not quickly merged into
master, automatic merging rapidly disappears and another round of manual mergings and modifications starts again.What I would expect is that merging
masternever introduces non passing tests into my current branch.I'm far from an expert with the organization of git repos with large teams but I think that we should try to solve this situation that is slowing down developments.
One thing that may be related with this issue is the fact that running tests is very slow. This makes feedback very slow.
/cc
@decidim/product @decidim/lot-core
📌 Related issues