Bundle Dependabot Updates

Create a PR that combines multiple open dependabot PRs into a single PR targeting master.

Arguments (Optional)

• •<target-branch> - Branch to create PR against (default: master)

Examples:

• •/bundle-dependabot - Combine dependabot PRs targeting master
• •/bundle-dependabot main - Use main as target branch

Instructions

Step 1: Setup - Checkout and Pull Target Branch

git checkout master
git pull origin master

Step 2: Identify Open Dependabot PRs

Find all open PRs from dependabot:

gh pr list --author "dependabot[bot]" --state open --json number,title,headRefName

If no open PRs are found, inform the user and exit.

List the PRs found and confirm with the user before proceeding.

Step 3: Create Feature Branch

Generate a branch name with today's date:

git checkout -b chore/dependabot-updates-$(date +%Y%m%d)

Step 4: Fetch and Merge Each PR

For each dependabot PR, fetch and merge with the original commit message:

# Fetch all dependabot branches
git fetch origin <branch-name-1> <branch-name-2> ...

# Merge each with --no-ff and proper commit message
git merge --no-ff origin/<branch-name> -m "<original PR title>"

Handling package-lock.json conflicts:

If a merge conflict occurs in package-lock.json:

git checkout --theirs package-lock.json
npm install
git add package-lock.json package.json
git commit -m "<original PR title>"

Step 5: Push and Create PR

git push -u origin HEAD

Create the PR in English:

gh pr create \
  --base master \
  --title "chore(deps): bundle dependabot updates" \
  --body "$(cat <<'EOF'
## Summary
Bundle multiple dependabot dependency updates into a single PR.

## Changes
<list of dependency updates from merged PRs>

## Notes
Use "Squash and merge" to combine into a single commit.
EOF
)"

Step 6: Output

Display:

1. •List of dependabot PRs that were merged
2. •The new branch name
3. •Link to the created PR

Error Handling

• •If no open dependabot PRs are found, inform the user and exit
• •If merge conflicts occur (other than package-lock.json), pause and ask the user how to proceed
• •If PR creation fails, show the error and the manual command to create it

Notes

• •Do NOT squash commits locally - GitHub's "Squash and merge" will handle that
• •Use the original dependabot PR title as the merge commit message
• •Always use --no-ff to create merge commits