[HACK WEEK] Add Dependabot & Dependency Tree Diff Configuration#16092
[HACK WEEK] Add Dependabot & Dependency Tree Diff Configuration#16092AliSoftware merged 6 commits intotrunkfrom
Conversation
This is a new 'ViolationCommentsToGitHubTask' that is going to be used alongside the dependency tree diff script to automatically add a PR comment with the dependency changes diff for reviewing purposes.
|
You can trigger optional UI/connected tests for these changes by visiting CircleCI here. |
bae1376 to
2aef057
Compare
|
You can test the changes on this Pull Request by downloading the APKs: |
2aef057 to
9c9bae4
Compare
9c9bae4 to
fde135e
Compare
|
I am not quick sure why the @kidinov any ideas? 🤔 🙏 |
Yeah you are right It works in the PR which is based on the current branch: #16096 (you can use this for testing too) If you want to improve this, then just save the current branch in a variable and then add
on line #45 |
|
Dependabot config looks good to me! I'll keep an eye now on Autostattic 👀. |
|
👋 @kidinov !
Thank you so much for double checking and actually testing this PR! 🙏 🥇 🚀
👍 Btw, how would this improve the script if I add it there? Wouldn't the logic change if I check-out the |
|
👋 @wzieba !
Thank you so much for the confirmation, and as always, for keeping an eye with Autostattic! 🙏 🥇 🚀 |
It won't change much, except it will fix the case you have right now in this PR, when on the target branch there is not task |
| - dependency-name: "com.android.tools.build:gradle" | ||
| # Bumping 1.2.1 to 1.3.0 causes some issues, fist spotted in Reader. For more details, see | ||
| # https://github.com/wordpress-mobile/WordPress-Android/pull/14431 | ||
| - dependency-name: "com.google.android.material:material" |
There was a problem hiding this comment.
I wouldn't recommend to ignore it - I believe sooner or later the bump will be necessary. Maybe it's worth to revisit and fix the issue?
There was a problem hiding this comment.
Thanksor for the review @wzieba ! 🙏
I wouldn't recommend to ignore it - I believe sooner or later the bump will be necessary.
Yes, you are right. I just chose to ignore it for now and deal with it explicitly because last time this simple update happened, noone noticed it and it almost when live until we noticed that some layouts are having problems. Thus, I felt that if we don't ignore it for now, when the bot will generate the PR, someone will smoke test it and potentially approve it without doing a thorough test or knowing this wierd correlation between Material and Constraint Layout.
Maybe it's worth to revisit and fix the issue?
What if I creat a specific Material update issue explaining all about the problems coming with it, that Constraint Layout is related somehow and might also need to be updated as well. Then, I can keep this ignoring rule and add a new comment line with the linked issue that should address it. Wdyt? 🤔
There was a problem hiding this comment.
Personally I'm ok with you creating a specific issue explaining all about the problem, as long as that issue does not end up in limbo and gets forgotten (maybe assigning it a Milestone to target it in a specific future sprint?)
I'd then recommend adding an additional comment on this line to point to said future issue.
There was a problem hiding this comment.
FYI: I created this accompanying #16132 issue for that matter, let me know what you think. 🙏
PS: I also added an extra link comment commit for that matter.
There was a problem hiding this comment.
Great, thank you so much @AliSoftware ! 🚀 🟢
There was a problem hiding this comment.
It's all good on my end, thanks for establishing strategy for handling this dependency!
| - dependency-name: "com.android.tools.build:gradle" | ||
| # Bumping 1.2.1 to 1.3.0 causes some issues, fist spotted in Reader. For more details, see | ||
| # https://github.com/wordpress-mobile/WordPress-Android/pull/14431 | ||
| - dependency-name: "com.google.android.material:material" |
There was a problem hiding this comment.
Personally I'm ok with you creating a specific issue explaining all about the problem, as long as that issue does not end up in limbo and gets forgotten (maybe assigning it a Milestone to target it in a specific future sprint?)
I'd then recommend adding an additional comment on this line to point to said future issue.
| # Bumping 1.2.1 to 1.3.0 causes some issues, fist spotted in Reader. For more details, see | ||
| # https://github.com/wordpress-mobile/WordPress-Android/pull/14431 | ||
| - dependency-name: "com.google.android.material:material" |
There was a problem hiding this comment.
Something like this, except be sure to update the link to the issue once you've created it.
| # Bumping 1.2.1 to 1.3.0 causes some issues, fist spotted in Reader. For more details, see | |
| # https://github.com/wordpress-mobile/WordPress-Android/pull/14431 | |
| - dependency-name: "com.google.android.material:material" | |
| # Bumping 1.2.1 to 1.3.0 causes some issues, first spotted in Reader. For more details, see | |
| # https://github.com/wordpress-mobile/WordPress-Android/pull/14431 | |
| # So we plan to handle the update manually later, to handle it in correlation with `Constraint Layout`; see | |
| # https://github.com/wordpress-mobile/WordPress-Android/issues/<link-to-issue> | |
| - dependency-name: "com.google.android.material:material" |
Generated by 🚫 dangerJS |
This PR adds Dependabot and Dependency Tree Diff tooling and related configuration to this repo. I chose to add both tools in one go because Dependabot will very much benefit from Dependency Tree Diff and ultimately help reviewers do their review more effectively.
Also as part of this work I created the following:
bot: dependencies updatelabel (see Bot Labels query). Dependabot is going to be using this label (see dependabot.yml configuration)Android Developersteam for the WordPress Mobile organization (see Android Teams query). Dependabot is going to be using this team as reviewers (see dependabot.yml configuration)As I am mainly copy-pasted the already existing configuration from
WCAndroid. I tried to be careful with the setup but I might be missing something obvious. As such, I am shamelessly mentioning @wzieba (for on Dependabot) and @kidinov (for Dependency Tree Diff) to help with this review in case I am missing something very obvious. PS: I even copy-pasted your testing instructions... 😅 But, on a more serious note, thank you both for all the work you did already on all that, thus making it so easy for me to follow your lead, you rock! 🪨Related
WCAndroidPRs:I'll also publish a P2 post next week (see NEW) notifying
WPAndroiddevelopers about this change and providing more details about the process going forward, mainly (and again) copy-pasting the existing process that is already in place withinWCAndroid.Related P2s:
paqN3M-qo-p2p91TBi-4N0-p2pbArwn-41v-p2To test (Dependabot):
To test (Dependency Tree Diff):
PS: You also can reference the below two test related draft PRs to verify correctness:
Regression Notes
N/A
N/A
N/A
PR submission checklist:
RELEASE-NOTES.txtif necessary.