Gather master CI feedback in a ci-participant issue - Githubissues

snowdrop-zen / quarkus

Quarkus: Supersonic Subatomic Java.

https://quarkus.io

Apache License 2.0

1 stars 0 forks source link

Gather master CI feedback in a ci-participant issue #181

Open snowdrop-bot opened 4 years ago

snowdrop-bot commented 4 years ago

It would be nice if we could track the status of master with an issue:

for the 1.7 and master branch
only if the repository is ours (i.e. we don't want it to report when on forks)
only for push events

In a perfect world, we could only trigger an issue when something is failing and consider having 1-2 cancelled steps as something tolerable.

Question is: will you have the secrets handy if it's a push event?

https://github.com/quarkusio/quarkus/issues/12195

$upstream:12195$