-
Notifications
You must be signed in to change notification settings - Fork 19
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
improvement: filters out special collections #868
improvement: filters out special collections #868
Conversation
Hello vrancurel,My role is to assist you with the merge of this Status report is not available. |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list: |
Create a function to identify special collections. Exclude collections starting with __ . Nevertheless keeping explicit naming on collections that are used directly by cloudserver even though they start with __ for sake of clarity. Include a unit test.
41d5a88
to
62536f6
Compare
@bert-e approve |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve |
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue ZENKO-2045. Goodbye vrancurel. |
Exclude collections starting with __
Nevertheless keeping explicit naming on collections
that are used directly by cloudserver even though they start with __
for sake of clarity