Add dependency dashboard #221
Conversation
This fixes a bug where the search returns mrs that are not related to the current dependency. For example searching for sidekiq also returns the sidekiq-status dependency.
|
What exactly do you mean by 1? Creating separate pipelines or just extracting the methods? |
|
@Tranquility both 🙂 |
|
Not sure I like that idea. We are basically just keeping statistics now and update the issue in the end. If we extract this into a new file we will either have a lot of duplication or we need to reorganize the whole project to prevent that. And moving it into a separate pipeline means we will have lot more ci jobs. Right now merging this branch should not change the behavior at all (except for the bug fix commit of cause) if the feature is not enabled. |
|
Ok, this makes sense! What about splitting this script into a separate file just for better readability? |
|
I think that makes sense in general. It would also improves the testabilty so we could add some tests as well. But I don't know when I will be able to work on that. |
|
No worries, @Tranquility! Take your time! |
This creates an issue for each language that contains all the dependencies that need updates. It looks like this:
Dependency Dashboard ruby
20 of 86 bundler dependencies are out of date.
It also fixes a bug with finding open merge requests. That I found because the dashboard lists the merge requests that belong to the dependency. The search returns all MRs that have the dependency name in the title. So the dependency dashboard listed the MR for sidekiq-status gem as MR for sidekiq.