* added PR creation to release action
Signed-off-by: Allison Suarez Miranda <asuarezmiranda@lyft.com>

* set new branch rather than master
Signed-off-by: Allison Suarez Miranda <asuarezmiranda@lyft.com>

* changed cron to 12:15pm
Signed-off-by: Allison Suarez Miranda <asuarezmiranda@lyft.com>

* chnaged release aciton branch and added manual run trigger
Signed-off-by: Allison Suarez Miranda <asuarezmiranda@lyft.com>

* eventually I'll get this right...
Signed-off-by: Allison Suarez Miranda <asuarezmiranda@lyft.com>

* another one
Signed-off-by: Allison Suarez Miranda <asuarezmiranda@lyft.com>

* one more branch change
Signed-off-by: Allison Suarez Miranda <asuarezmiranda@lyft.com>

* trying to get the branch there so it can be checked out
Signed-off-by: Allison Suarez Miranda <asuarezmiranda@lyft.com>

* added pypy credentials
Signed-off-by: Allison Suarez Miranda <asuarezmiranda@lyft.com>

* chaged to uses/with
Signed-off-by: Allison Suarez Miranda <asuarezmiranda@lyft.com>

* bumped version on setup.py file
Signed-off-by: Allison Suarez Miranda <asuarezmiranda@lyft.com>

* added pypi user and pass
Signed-off-by: Allison Suarez Miranda <asuarezmiranda@lyft.com>

* setting base branch to be master
Signed-off-by: Allison Suarez Miranda <asuarezmiranda@lyft.com>

* delete branch after pr closed
Signed-off-by: Allison Suarez Miranda <asuarezmiranda@lyft.com>

* trying a different more granular approach, pypi should be triggered once PR with new version is merged
Signed-off-by: Allison Suarez Miranda <asuarezmiranda@lyft.com>

* publishes new release
Signed-off-by: Allison Suarez Miranda <asuarezmiranda@lyft.com>

* fixed
Signed-off-by: Allison Suarez Miranda <asuarezmiranda@lyft.com>

* hoping this works, will add changelog next if it does
Signed-off-by: Allison Suarez Miranda <asuarezmiranda@lyft.com>