Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE REQUEST] Migrate to trunk based development #1933

Open
1 task done
Snailedlt opened this issue Oct 24, 2023 · 1 comment
Open
1 task done

[FEATURE REQUEST] Migrate to trunk based development #1933

Snailedlt opened this issue Oct 24, 2023 · 1 comment

Comments

@Snailedlt
Copy link
Collaborator

I have searched through the issues and didn't find my problem.

  • Confirm

Problem

Currently we are using a workflow similar to GitFlow and have two major branches: master and develop.

This causes a lot of overhead when it comes to releases, and can make things overly complicated.

Possible Solution

A much simpler approach would be to just have a single master or main branch, and merge all PR's into that. Then once we have something shippable all we have to do is run a workflow to make the release.

Additional information

In order to make the transition to trunk based development there's a large amount of automation scripts that need to be modified. The good thing is that there will also be quite a few that we can get rid of entirely. For example the in-develop-labeler.
Going to a trunk based development model will drastically improve our agility, and reduce the project's complexity

@Snailedlt
Copy link
Collaborator Author

I suggest we start on this right after the next release!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: To-do
Development

No branches or pull requests

1 participant