testcontainers / testcontainers/testcontainers-java
Combine many dependabot PRs into one
まだ誰も着手していません。
- 主要言語
- Java
- スター
- 8.7k
- フォーク
- 1.9k
- 平均マージ
- 2日 17時間
- マージ済み PR(30日)
- 9
説明
#4135 explored a scripted approach (running client side) of combining multiple PRs into one.
The motivation is that the sheer volume of dependabot PRs creates a weekly multi-hour merge chore, as well as obscuring real PRs by real people - both of which are terrible.
https://github.com/dependabot/dependabot-core/issues/1190 looks like it won't happen any time soon.
https://www.hrvey.com/blog/combine-dependabot-prs looks very promising and I think we should give it a try instead of my previous script attempt. I'd like to verify:
- that, as seen in #4135, we can have the release notes updates automatically. We'd need to:
- enable merge commits in this repo, and make sure we use them when merging the combined PR
- (I think) update our release-drafter workflow triggers, so that pull request events trigger release drafter. Even if not required, we should probably do that anyway.
- that merge conflicts are not too big a problem. We'll likely seem them occurring with changes in adjacent lines in
build.gradlefiles, which may or may not be a nuisance.- if merge conflicts are a problem, I have written a dirt-simple git merge driver script which seems to work well enough for
build.gradlefiles - perhaps we could explore using this.
- if merge conflicts are a problem, I have written a dirt-simple git merge driver script which seems to work well enough for
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
調査の方向性
まず #4135 と、issue で参照されている release-drafter workflow を確認します。Dependabot PRs と merge commits を組み合わせたときに release notes が正しく更新されるかをテストし、次に build.gradle ファイルの merge conflicts を評価します。workflow が信頼でき、conflicts が管理可能であれば完了です。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- git, github-actions
- 領域
- build-system, ci-cd, release
- issue の種類
- 機能追加
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 停滞
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 28/100