Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Danger support #366

Merged
merged 3 commits into from Dec 8, 2016
Merged

Danger support #366

merged 3 commits into from Dec 8, 2016

Conversation

tbaranes
Copy link
Member

That aim to close #362
In order to that, I had to create a github bot, and a gmail account. I will slack the credentials directly.

The Dangerfile is a first version, I think we should improve it following our future needs, but it's a good start.

Now, wait & see if everything is working 馃槵

@tbaranes tbaranes force-pushed the feature/danger branch 15 times, most recently from 553d938 to 8c88824 Compare November 29, 2016 10:06
@tbaranes
Copy link
Member Author

All good but...

Danger does not have write access to the PR to set a PR status.

Anyone has experienced with Danger or github tokens?

@mmadjer
Copy link
Contributor

mmadjer commented Nov 29, 2016

Not sure if this is related but you saw this issue?
danger/danger#117

@tbaranes
Copy link
Member Author

Yeah, I find that one when I looked into Danger issues, but didn't find any solution in it.
I'm waiting for travis to see if my last test did change something or not, otherwise I will probably answer in that thread or open a new issue to get help.

@JakeLin
Copy link
Member

JakeLin commented Nov 30, 2016

I am new to Danger. I have fired a ticket to Travis CI via support@travis-ci.com , will keep you guys posted once I got back anything.

@JakeLin
Copy link
Member

JakeLin commented Dec 4, 2016

Travis has fixed the build issue. It was an issue of their OS X infrastructure.

Hey Jake,

Thanks for reaching out and I'm sorry for this issue.

Unfortunately, we are currently still working on fixing an incident with our OS X infrastructure:

https://www.traviscistatus.com/incidents/nq0sf0srvx8s

This is most probably the reason why your build is currently delayed. Sorry for the inconvenience.

We are constantly giving status updates on the page linked above so I would suggest keeping an eye on it to see where we stand.

Thank you for your understanding.

Sincerely,

-- Dominic.

@tbaranes can we merge this PR now? Or we still need to fix ?

Danger does not have write access to the PR to set a PR status.

@tbaranes
Copy link
Member Author

tbaranes commented Dec 4, 2016

Danger is still not working, not sure due to the write access, not sure what we should do to fix it.

@JakeLin
Copy link
Member

JakeLin commented Dec 6, 2016

@tbaranes I am new to Danger. They said it should be fixed in danger/danger#380, but I don't know why our one can't pass?

@tbaranes
Copy link
Member Author

tbaranes commented Dec 6, 2016

We should open an issue there to ask more information about this. First time I setup a danger too (I just follow their steps). I will do it once I have more time to take care of this!

@JakeLin
Copy link
Member

JakeLin commented Dec 6, 2016

Thanks @tbaranes I need more time to learn how Danger works.

@tbaranes
Copy link
Member Author

tbaranes commented Dec 7, 2016

Issue opened there: danger/danger#675

@tbaranes
Copy link
Member Author

tbaranes commented Dec 8, 2016

After some discutions with Danger Team and github support, it seems to be working! I'm merging this now, but it's possible the global system (to give write access to the bot) may change again later.

Also, it's now time to play around with the Dangerfile 馃帀

@tbaranes tbaranes closed this Dec 8, 2016
@tbaranes tbaranes reopened this Dec 8, 2016
@tbaranes tbaranes merged commit 876ce21 into master Dec 8, 2016
@tbaranes tbaranes deleted the feature/danger branch December 8, 2016 07:34
@JakeLin
Copy link
Member

JakeLin commented Dec 8, 2016

Wa, thanks for following this up @tbaranes, big step 馃帀馃帀馃帀 Danger team is very helpful too.

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

Successfully merging this pull request may close these issues.

Setup Danger to check code style before merging PR
3 participants