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

Excluding branches #135

Closed
jakirkham opened this Issue Apr 8, 2015 · 4 comments

Comments

Projects
None yet
3 participants
@jakirkham
Copy link

jakirkham commented Apr 8, 2015

It would be nice if we could exclude some branches (e.g. gh-pages). There is no point in you guys checking it if we know it has no Python code.

@ssokolow

This comment has been minimized.

Copy link

ssokolow commented Apr 8, 2015

...but, at the same time, it'll have to be optional because, sometimes, I'll use the gh-pages branch as the master branch for things like repositories of small scripts where it makes more sense for the .py files to be mixed into the same folder tree as the website.

@jakirkham

This comment has been minimized.

Copy link
Author

jakirkham commented Apr 8, 2015

Absolutely, either some web GUI thing or some text for the YAML file (like what Travis does). I'd lean towards the latter, but either would be acceptable.

@ssokolow

This comment has been minimized.

Copy link

ssokolow commented Apr 8, 2015

I'd prefer the latter too. I maintain a comprehensive exit strategy in case any part of a project's service fabric goes bankrupt or turns evil and the biggest pains in the butt are the things like GitHub Issues and Releases that aren't automatically backed up by the git pull cronjobs I run on each project's main and wiki repositories.

@carlio

This comment has been minimized.

Copy link
Member

carlio commented Dec 10, 2015

I solved this the easy way by simply hiding failed checks which happen on branches called gh-pages. Feel free to reopen if you think it needs to be more configurable than that!

@carlio carlio closed this Dec 10, 2015

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