Githawk: Fork PR not triggering CI check

Created on 26 Feb 2018  路  5Comments  路  Source: GitHawkApp/GitHawk

Happening all the time in Bitraise.

Some recent PR's

  • #1543
  • #1550
  • #1589
馃幆 project management
Source
picture rizwankce

Most helpful comment

I assume that's a security precaution as otherwise forks can read environment variables.

picture BasThomas on 26 Feb 2018
👍2

All 5 comments

I assume that's a security precaution as otherwise forks can read environment variables.

BasThomas picture BasThomas on 26 Feb 2018
👍2

Worth noting that most providers have an option to enable/disable it, so maybe one for Ryan to make the decision on? (Especially since the env vars have been public more times than anyone cares to admit 馃槀)

Sherlouk picture Sherlouk on 26 Feb 2018

Trying to wrap my head around where this isn't working. I don't share secrets w/ PRs, but even if that's the case why aren't PRs triggering a workflow that fails unit tests? @viktorbenei any tips on what I'm missing?

rnystrom picture rnystrom on 27 Feb 2018

@rnystrom I'm off today, happy to help tomorrow if that's OK or feel free to ping our support!

viktorbenei picture viktorbenei on 27 Feb 2018
👍1

Actually I'd suggest you to check this troubleshooting guide first http://devcenter.bitrise.io/webhooks/troubleshooting/

Bitrise returns the exact reason why it did not start a build, which you can see in github repo webhook settings, as well as on Bitrise (activity page).

If that wouldn't help just let me know 馃槈

viktorbenei picture viktorbenei on 27 Feb 2018
👍1
Was this page helpful?
0 / 5 - 0 ratings

Related issues

weyert picture weyert  路  3Comments
rnystrom picture rnystrom  路  3Comments
rnystrom picture rnystrom  路  3Comments
BasThomas picture BasThomas  路  3Comments
BasThomas picture BasThomas  路  3Comments