You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As per ansible-community/stats-collections#19 there are bots we should exclude. Having that config here at the top-level of the data collection pipeline is probably the right place for it, so other apps and dashboard can get it from a single source, and where the community can provide updates.
Current list to exclude:
patchback
modular-magician
ansibullbot
The text was updated successfully, but these errors were encountered:
Create lists of things that we wish to differentiate (such as bots vs people, collections vs other repos, etc)
Have that in one place so that everyone knows where to update it
Each stats thing we build consumes that hand-crafted config in it's own way
As an example, the internal reports I'm doing would use this to filter collections, but a report on other repos wouldn't have to. We also have the option to refine this config over time, so long as we know which apps make use of which config (i.e. the "config backlinks").
As per ansible-community/stats-collections#19 there are bots we should exclude. Having that config here at the top-level of the data collection pipeline is probably the right place for it, so other apps and dashboard can get it from a single source, and where the community can provide updates.
Current list to exclude:
The text was updated successfully, but these errors were encountered: