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

StyleCI Config Gone #69

Closed
GrahamCampbell opened this issue Dec 30, 2015 · 9 comments
Closed

StyleCI Config Gone #69

GrahamCampbell opened this issue Dec 30, 2015 · 9 comments

Comments

@GrahamCampbell
Copy link
Contributor

No description provided.

@GrahamCampbell
Copy link
Contributor Author

I'd recommend you just add it in https://styleci.io/repos/10456191/settings, and don't bother with any local tools. The whole point of styleci is to avoid that.

@GrahamCampbell
Copy link
Contributor Author

Ping @cirpo. If you need any help with StyleCI just let me know.

@GrahamCampbell
Copy link
Contributor Author

Would you like me to update the config for you to match your current cs?

@cirpo
Copy link
Contributor

cirpo commented Dec 30, 2015

@GrahamCampbell yes, please :)

I wouldn't remove the local config/tools because it's still handy to run them locally instead of always getting failures from StyleCi.

@GrahamCampbell
Copy link
Contributor Author

I wouldn't remove the local config/tools because it's still handy to run them locally instead of always getting failures from StyleCi.

StyleCI can automatically push the fixes for you you know, if you enable auto sending and auto merging of fix PRs in the config.

@GrahamCampbell
Copy link
Contributor Author

I've updated the config for you: https://i.starbs.net/J3z3. Let me know if that's not correct.

@GrahamCampbell
Copy link
Contributor Author

@GrahamCampbell
Copy link
Contributor Author

It gives that result. If you like the changes, just hit the send fix PR button at the top.

@GrahamCampbell
Copy link
Contributor Author

I can't remember if you wanted long or short arrays, so you might want to change that line. ;)

@cirpo cirpo closed this as completed Jan 13, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants