-
Notifications
You must be signed in to change notification settings - Fork 22
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
Removing unused filteringTerms.yaml & json files #167
base: clean-up
Are you sure you want to change the base?
Conversation
@jrambla @costero-e Just a note: This PR is against |
IMHO, we (should?) have four main branches: main, develop, fixes & cleanup... |
Well, we should have one to drop things in which have been reviewed and which is always updated from main, and then do minor version updates with some collected changes. Otherwise it becomes a bit messy if you want to track back... But I'm certainly fine with doing "collective merge + version bump" sessions :-) |
In my view: all/most branches should have reviews, all of them should merge into main and all changes should be assigned to a version. |
Hi @jrambla, yes, it makes sense to have these branches with a cleanup branch. Let me update the cleanup branch to make these cleanups mergeable. |
This PR is to remove the unused filteringTerms files, according to issues #159 , #93