Repository: bulk-changer

Command-line tools for bulk raising PRs across GOV.UK repos.

• GitHub: bulk-changer
• Ownership: #govuk-platform-engineering
• Category: Utilities

README

To run RSpec and RuboCop:

bundle exec rake

Required GitHub permissions

In order to run any of these commands, you will need to generate a personal access token, with:

• Resource owner: alphagov
• Repository access: All repositories
• Repository permissions:
  • Contents: read and write
  • Pull requests: read and write
  • Workflows: read and write (only required if you will be using Bulk Changer to create or modify GitHub Actions workflows)

Commands

bulk-update-file

Ensures that a file exists in every GOV.UK repo, at the given path, with the given contents. If the file does not currently exist, or if its contents do not match the desired contents, then raises a PR to create or update the file.

usage: ./bulk-update-file [options]
    -h, --help          print this usage information
    --dry-run           simulate filtering repositories, but do not actually raise pull requests
    --github-token      GitHub API token

--file-path         path to the file to create/update (required)
--file-content      desired content of the file (required)
pull request options:
    –branch            name of the branch to commit the change to (required)
    –pr-title          title for the PR to raise (required)
    –pr-description    description of the PR to raise (required)
filtering options:
    –if-any-exist      only raise a PR if any of the given paths exist on the main branch (may be specified multiple times)
    –if-all-exist      only raise a PR if all of the given paths exist on the main branch (may be specified multiple times)
    –unless-any-exist  only raise a PR if any of the given paths do not exist on the main branch (may be specified multiple times)
    –unless-all-exist  only raise a PR if all of the given paths do not exist on the main branch (may be specified multiple times)

bulk-replace

Look for a file in every GOV.UK repo, at the given path, with the given content and replace with new content. If the file does not currently exist, or if it doesn’t have the given content, then that repo is skipped, otherwise a PR is raised. If the branch already exists, a new commit can be added to it.

usage: ./bulk-replace [options]
    -h, --help                       print this usage information
    --github-token                   GitHub API token

--file-path                      path to the file to update (required)
--old-content                    content to be replaced in file (required)
--new-content                    new content for file (required)
--global                         replace all occurrences of content (true by default)
pull request options:
    –branch                         name of the branch to commit the change to (required)
    –pr-title                       title for the PR to raise
    –pr-description                 description of the PR to raise
    –commit-title                   title for the commit (required)
    –commit-description             description of the commit (required)
    –use-regex                      use a regex pattern to find content (false by default)
    –continue-on-existing-branch    automatically confirm all ‘Continue on existing branch?’ questions (false by default)
    –file-path-is-regex             use a regex pattern to find file paths (false by default)

Examples

Create workflows to copy PR template onto Dependabot PRs

Several alphagov repositories contain pull request templates, to warn requesters about things like the fact that the repo is continuously deployed, that the repo requires manual pre- or post- merge steps, or that the repo lacks an automated test suite.

The pull requests that Dependabot raises do not use these templates, which has led to issues in the past where reviewers have assumed that a Dependabot PR was safe to merge, when it was not.

To find every GOV.UK repo that contains a pull request template, and automatically raise a PR to add a GitHub Actions workflow^workflow that will post the pull request description as a comment on each pull request that Dependabot raises (this requires a GitHub API token with the workflow scope):

./bulk-update-file \
    --dry-run \
    --github-token "..." \
    --branch copy-pr-template-to-dependabot-prs \
    --pr-title "Create workflow to copy PR template onto Dependabot PRs" \
    --pr-description "$(<./templates/copy-pr-template-to-dependabot-prs.pr-description.md)" \
    --file-path ".github/workflows/copy-pr-template-to-dependabot-prs.yaml" \
    --file-content "$(<./templates/copy-pr-template-to-dependabot-prs.yaml)" \
    --if-all-exist ".github/dependabot.yml" \
    --if-any-exist "pull_request_template.md" \
    --if-any-exist "docs/pull_request_template.md" \
    --if-any-exist ".github/pull_request_template.md"

<!– raw HTML omitted –>