Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

fix deployment to work w/ a fully-protected branch #3915

Closed
chadwhitacre opened this issue Feb 9, 2016 · 5 comments
Closed

fix deployment to work w/ a fully-protected branch #3915

chadwhitacre opened this issue Feb 9, 2016 · 5 comments
Labels

Comments

@chadwhitacre
Copy link
Contributor

We protected master at gratipay/inside.gratipay.com#487 (comment). First deploy since then reveals a problem:

remote: -----> Launching...
remote:        Released v1566
remote:        https://gratipay.herokuapp.com/ deployed to Heroku
remote:
remote: Verifying deploy.... done.
To [email protected]:gratipay.git
   4dd7fec..2c5ccd2  master -> master
Counting objects: 14, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (13/13), done.
Writing objects: 100% (14/14), 1.37 KiB | 0 bytes/s, done.
Total 14 (delta 9), reused 0 (delta 0)
remote: error: GH006: Protected branch update failed for refs/heads/master.
remote: error: Required status check "continuous-integration/travis-ci" is expected
To [email protected]:gratipay/gratipay.com.git
 ! [remote rejected] master -> master (protected branch hook declined)
error: failed to push some refs to '[email protected]:gratipay/gratipay.com.git'
$

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@chadwhitacre chadwhitacre changed the title fix deployment w/ protected branch fix deployment to work w/ a fully-protected branch Feb 9, 2016
@chadwhitacre
Copy link
Contributor Author

I relaxed the protection for admins as a workaround.

screen shot 2016-02-09 at 3 06 52 pm

@chadwhitacre
Copy link
Contributor Author

I made a @gratipay/deployers team w/ @rohitpaulk @clone1018 and myself with admin access on the repo so we can deploy.

@chadwhitacre
Copy link
Contributor Author

Looks like all three of us have 2FA set up, which is good.

@nobodxbodon
Copy link
Contributor

Seems like done in short term. BTW issues like this seem to be better in inside.gratipay.com to me.

@chadwhitacre
Copy link
Contributor Author

Seems like done in short term.

Does it? How?

BTW issues like this seem to be better in inside.gratipay.com to me.

Why? The issue is specific to gratipay.com, no?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants