deploy
deploy copied to clipboard
remind101
CLI for GitHub Deployments
Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.0.0-20210513164829-c07d793c2f9a to 0.1.0. Commits See full diff in compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Say you're on master locally, if you `deploy -e production` it's possible that it's going to deploy an older version because someone has pushed remote master after you last pulled....
Last I checked, it was broken. https://github.com/remind101/homebrew-formulae is a better way for us to distribute new versions.
If the .git/config url is missing `.git` on the end, you get an error: **Example** ``` [remote "origin"] url = [email protected]:remind101/acme-inc ``` ``` console $ deploy Invalid GitHub repo: /remind101/acme-inc...
Might be good to add something along the lines of https://github.com/inconshreveable/go-update, just to make it easier to make changes without having to tell everyone to update.
Right now we show the Tugboat status URL, but you have to copy/paste to a browser to view it. A `deploy open` command or something to that effect for the...
This would be kind nice, especially as we move things to docker, where we can't deploy until the image is built (commit status checks pass). This flag would cause the...
GitHub doesn't actually have support for this, so something to think about for the future.
From @dustinhorton: ``` console ~/Sites/r101/r101-viewer (asset-host) →deploy --env=staging --force Invalid GitHub repo: /remind101/r101-viewer ``` ``` console →cat ~/Sites/r101/r101-viewer/.git/config [remote "origin"] url = [email protected]:remind101/r101-viewer fetch = +refs/heads/*:refs/remotes/origin/* ```