add endpoints to bulk delete collections/groups

[stefan0xC]

I'm not sure if this is the best way but this should fix #3350

[tessus]

Hmm, hasn't BlackDex just moved the clientIP to the headers?

[tessus]

Quick question, since I am new to Rust and this code base, is there a guide to understand what these impl From<ManagerHeaders> for ManagerHeadersLoose (just an example, since there are a bunch of them) constructs are?
You can mark this comment as off-topic, I just didn't know where to ask. It seemed superfluous to open a discussion for that question.

[dani-garcia]

Just a small comment, not a big deal in normal usage though

[BlackDex]

It only needs a rebase now i think :)

[stefan0xC]

It only needs a rebase now i think :)

into a single commit?

[BlackDex]

It only needs a rebase now i think :)

into a single commit?

I would do a force push.
So.. basically these are the steps (from the top of my head)

git checkout main
git pull
git fetch --all --tags
git rebase upstream/main
git push origin main

git checkout -b bulk-delete-endpoints
git rebase origin/main
git push origin +bulk-delete-endpoints

[tessus]

I would do a force push.

@BlackDex I ususally do a squash and merge when merging PRs, thus there will only be a single commit anyway. I gave up on merge commits a long time ago. There are a few exceptions, but even those are getting less and less. ;-)

Just out of curiosity, when do you do a rebase? I only do a rebase, if I have to pull in code from the main branch, but others merge main to the PR branch. It's always interesting to find out how others are handling this.

[BlackDex]

The rebase is only needed because the code has been updated like 3 hours ago or something. Thus it needed to be based upon that. Squashing is fine for creating one commit indeed.