Metadata-Version: 2.1
Name: birdseye-remotes
Version: 0.1.1
Summary: CLI tool for comparing the heads of local and remote git repositories
Home-page: https://github.com/cursive-works/birdseye
Author: Patrick Smith
Author-email: pat.smith@cursive.works
License: MIT
Keywords: git remote information summary
Classifier: Development Status :: 3 - Alpha
Classifier: Topic :: Utilities
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Programming Language :: Python :: 3.9
Classifier: Programming Language :: Python :: 3.10
Classifier: License :: OSI Approved :: MIT License
Requires-Python: >=3.7
Description-Content-Type: text/markdown
Requires-Dist: GitPython

# Birdseye
 A tool for comparing git hashes across local and multiple remotes.
 It's purpose is to add confidence and speed when deploying via git to Heroku;
 esp. when you have production and stage services to manage.

 It requires that you set up your multiple app/environments as outlined by
 Heroku here: https://devcenter.heroku.com/articles/multiple-environments

## Installation
Birdseye is a CLI tool and so it's a good idea to install it via [pipx https://pypa.github.io/pipx/

```sh
pipx install birdseye-remotes --index-url=https://pypi.cursive.works
```

## Repo sConfiguration
```sh
# see what you've got:
git remote -v
# rename existing `heroku` remote accordingly:
git remote rename heroku (stage | production)
# add remaining remote(s) as needed:
heroku git:remote -a APP --remote (stage | production)
```

```sh
# Set a default environment
git config heroku.remote stage
```


## Developing
```sh
git clone git@github.com:waldo90/birdseye
cd birdseye
python3 -m venv venv
```

On subsequent sessions
```sh
 . ./venv/bin/activate
 pip install -r requirements.txt
```
