-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set up Heroku team #17
Comments
@crablar can you add access to the Podsheets github repo for Heroku? I want to create a new pipeline owned by the Heroku Podsheets team that pulls from the Podsheets repo |
Created pipeline
…On Tue, Jul 9, 2019 at 1:16 PM Andrew Lloyd ***@***.***> wrote:
@crablar <https://github.com/crablar> can you add access to the Podsheets
github repo for Heroku? I want to create a new pipeline owned by the Heroku
Podsheets team that pulls from the Podsheets repo
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#17?email_source=notifications&email_token=AAJZIEWEKYFWGGDAHQ4M4JLP6TW3NA5CNFSM4H7IMZUKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZRMX4Q#issuecomment-509791218>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJZIEWDGGHRTWKIIPG6333P6TW3NANCNFSM4H7IMZUA>
.
--
Thanks,
Jeff Meyerson
Host of Software Engineering Daily
<http://www.softwareengineeringdaily.com/>
@the_prion on Twitter
512-217-0273
|
I don't see the pipeline in Heroku. Could be a permission issue? |
I think this is what we want: https://github.com/settings/connections/applications/2bde25e3844dcbccc16d |
Can you view this? https://dashboard.heroku.com/pipelines/6391440e-43ec-4db2-b817-276105c963a6 |
Yeah this is perfect thanks.
… On Jul 13, 2019, at 12:19, Jeffrey Meyerson ***@***.***> wrote:
Can you view this? https://dashboard.heroku.com/pipelines/6391440e-43ec-4db2-b817-276105c963a6
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
No description provided.
The text was updated successfully, but these errors were encountered: