
Security News
Browserslist-rs Gets Major Refactor, Cutting Binary Size by Over 1MB
Browserslist-rs now uses static data to reduce binary size by over 1MB, improving memory use and performance for Rust-based frontend tools.
delete-merged-branch
Advanced tools
A GitHub app built that automatically deletes a branch after it's merged. That's it, enjoy!
Want to see more badges? Click here!
Want to run this app with GitHub Actions? Click here
A GitHub app built with Probot that automatically deletes a branch after it's merged. That's it, enjoy!
You may not need this app as GitHub recently added this feature natively to their platform. It allows you to automatically delete the head branch after a merge. If you need more advanced controls and configuration settings, this app is still well suited for the job.
First, follow these instructions for making your own GitHub app.
Then, clone the repo:
git clone git@github.com:SvanBoxel/delete-merged-branch.git
Copy .env.example
to .env
and set the right environment variables as here
Now, install app dependencies and run it:
# Install dependencies
npm install
# Run the bot
npm start
Make sure you have docker installed.
Follow the same steps as running locally to set up the GitHub app and environment files.
Build the docker image:
docker build -t delete-merged-branch .
Run the docker image:
docker run -i -t --rm \
-v "$(pwd)/.env:/app/.env" \
-p 3000:3000 \
delete-merged-branch
Alternate Example: Running test in the docker image
docker run -i -t --rm \
-v "$(pwd)/.env:/app/.env" \
-v "$(pwd)/sample-data:/sample-data" \
delete-merged-branch \
receive /app/index.js -p /sample-data/event.json
This GitHub app listens to the pull_request.closed
webhook. If a pull request is closed and the connected branch is merged, it will delete the branch.
The optional app configuration YAML file should be saved as .github/delete-merged-branch-config.yml
. At the moment it supports the following options:
exclude
(array) - list of branches that should not be automatically deleted after a merge. Wildcards supported.delete_closed_pr
(bool) whether or not a branch should be deleted if PR is closed without mergingExample .github/delete-merged-branch-config.yml
:
exclude:
- development
- qa
- feature-*
delete_closed_pr: true
CI (Travis) is in charge of releasing new versions of the GitHub Application to Now. On every new commit to master we run semantic-release to determine whether the major/minor/patch version should be incremented. If so, we update the version running in production.
This app is compatible with GitHub Actions. You need to create a workflow that is triggered on the pull_request
event for this. Then, you use this repo for the action. (SvanBoxel/delete-merged-branch@master
). Don't forget to check the GITHUB_TOKEN
secret. That's it.
If you have suggestions for how this GitHub app could be improved, or want to report a bug, open an issue! We'd love all and any contributions.
For more, check out the Contributing Guide.
ISC © 2018 Sebass van Boxel hello@svboxel.com
FAQs
A GitHub app built that automatically deletes a branch after it's merged. That's it, enjoy!
The npm package delete-merged-branch receives a total of 8 weekly downloads. As such, delete-merged-branch popularity was classified as not popular.
We found that delete-merged-branch demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Browserslist-rs now uses static data to reduce binary size by over 1MB, improving memory use and performance for Rust-based frontend tools.
Research
Security News
Eight new malicious Firefox extensions impersonate games, steal OAuth tokens, hijack sessions, and exploit browser permissions to spy on users.
Security News
The official Go SDK for the Model Context Protocol is in development, with a stable, production-ready release expected by August 2025.