Delete unused branches

[mtrezza]

New Feature / Enhancement Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.

Current Limitation

As we are moving to our org wide branch model as part of #668, let's delete the unused branches.

Feature / Enhancement Description

The goal is to remove all branches except for master. I already deleted the release branches release/... which only served to prepare the releases it seems. The tags are still here to point to the releases.

What about these branches:

• development
• feature/batch_saving

I assume developement was used to merge features before merging them into master. The branch doesn't seem necessary anymore and it shouldn't contain any code that isn't also in master. If someone can confirm this, I'll go ahead and delete it. We are directly merging into master for now - in absence of a pre-release strategy, which makes most sense once we have fully automated releases, see #668.

The batch_saving branch looks like it should be a PR, but it's also an old branch from 2020. Can anyone confirm whether this feature has already been merged, has become obsolete, or the branch code should be preserved for future development? In the latter case, does anyone want to pick this up? Is there a related issue?

Example Use Case

n/a

Alternatives / Workarounds

n/a

[parse-github-assistant]

Thanks for opening this issue!

• 🎉 We are excited about your ideas for improvement!

[mtrezza]

cc @RodrigoSMarques @fischerscode @phillwiggins

[RodrigoSMarques]

@mtrezza
The development branch is used before merging into master.

The master branch is used to keep the latest version available in production.

Then I create releases from the master's code versions. This is the flow I've been working on in git.

I don't know the batch_saving branch.

If the merge was not done, it is out of date.

If possible, keep the branch for a while to compare the code that has changed and evaluate the rewrite and a new PR.

[mtrezza]

• I think we can delete the development brach, the compare doesn't show any commits except for the newer ones we did on master recently - would you agree?

• Could you or @fischerscode take a look at the batch_saving, what it is and whether we still need the code there? Since we don't host PR branches in the repo anymore, it would also be great if someone could at least open a PR with it, so we can remove the branch.

[fischerscode]

batch_saving

I'll have a look at it in a few hours.
Most likely I'll bring it to my fork to save the code.

[fischerscode]

@mtrezza
I archived feature/batch_saving in my branch. link

You can delete it now.

If we add batch operations in the future, we can use the branch in my fork for reference, but we won't merge the changes from back then, esp. since back then null safety was not a thing.

[mtrezza]

Great, thanks, I'll go ahead and remove all branches except for master.