https://github.com/patrickduncan/lagging_branches
Easily find out which branches need rebasing
https://github.com/patrickduncan/lagging_branches
Last synced: about 1 month ago
JSON representation
Easily find out which branches need rebasing
- Host: GitHub
- URL: https://github.com/patrickduncan/lagging_branches
- Owner: PatrickDuncan
- Created: 2018-06-14T02:44:26.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2018-06-14T16:00:25.000Z (about 8 years ago)
- Last Synced: 2025-01-25T05:41:25.480Z (over 1 year ago)
- Language: Shell
- Size: 1.95 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
## Lagging Branches
Every large project experiences an issue where some feature branches end up lagging behind the core development. When a developer starts to develop that feature again they will most likely run into a plethora of conflicts.
One way to avoid this issue is to use this tool! This tool lists every branch that is behind another branch and displays how far behind they are.
### Requirements
- sh
### Installation
1. Clone this repository
2. Enter your project
3. Run `.//lagging_branches.sh [Options]`
### Options
`lagging_branches.sh [Branch] [Remote] [Fetch]`
#### Branch
The branch to compare all the other branches to.
*Default: master*
#### Remote
The remote name to get the branches from.
*Default: origin*
#### Fetch
Whether you want to the script to fetch the remote (it also prunes). Anything other than the default will fetch.
*Default: no*
### Example
`.//lagging_branches.sh new-users staging yes`