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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

don't run service tests on master; test on [packagist] #2392

Merged
merged 3 commits into from
Dec 4, 2018

Conversation

chris48s
Copy link
Member

Is this a sensible thing to do? I wonder if CIRCLE_BRANCH any more reliably populated than CI_PULL_REQUEST ?

Running tests on [packagist] just to check the tests still run on pull requests

refs #2388

@shields-ci
Copy link

Messages
📖 ✨ Thanks for your contribution to Shields, @chris48s!

Generated by 🚫 dangerJS

@paulmelnikow
Copy link
Member

Huh, I think using a branch filter on the job would be more reliable (like we do with the gh-pages).

@paulmelnikow paulmelnikow added the developer-experience Dev tooling, test framework, and CI label Nov 26, 2018
@paulmelnikow
Copy link
Member

Sorry; I had not noticed this was updated!

@chris48s chris48s merged commit bca9df2 into badges:master Dec 4, 2018
@shields-deployment
Copy link

This pull request was merged to master branch. This change is now waiting for deployment, which will usually happen within a few days. Stay tuned by joining our #ops channel on Discord!

After deployment, changes are copied to gh-pages branch:

@paulmelnikow
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
developer-experience Dev tooling, test framework, and CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants