Startrekzky commented on issue #5002: URL: https://github.com/apache/incubator-devlake/issues/5002#issuecomment-1685776063
Hi @EvanChen1989 , > 1. Newly created repos usually are needed to collect, resources are usually put under other groups. And even when they're put in wrong place, we're happy to filter them out during analysis other than picking the right ones into selection frequently. What do you mean by 'filtering them out during analysis'? Do you mean that you can move the automatically-added-new repos to the right DevLake blueprints if they're placed in the wrong blueprint at the first place? > 4. We create different blueprints for different groups, and due to some historical problems certain groups contains a large number of repos. Now I'm splitting them into 4 grouops divided by alphabetic cuz when we found no data for certain repo, it's a nightmare to search through the blueprint and find if it's included...it's not even sorted during display :( - What DevLake version are you on? After v0.17.0, we bind the blueprint to DevLake projects, users are not allowed to create independent blueprints anymore. Can you upgrade to [v0.18.0-beta6](https://github.com/apache/incubator-devlake/releases/tag/v0.18.0-beta6) to try the latest version out? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
