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.

Sign up for GitHub

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

Jump to bottom

Enable Hakiri for new org #29

Closed
2 tasks done
amoose opened this issue Jan 23, 2016 · 4 comments
Closed
2 tasks done

Enable Hakiri for new org #29

amoose opened this issue Jan 23, 2016 · 4 comments
Assignees
@jgrevich

Comments

@amoose
Copy link
Member

amoose commented Jan 23, 2016

https://hakiri.io/github/jgrevich/fugacious/dev

  • Please enable Hakiri for new org.
  • Update badge in readme
@amoose
Copy link
Member Author

amoose commented Jan 26, 2016

Complete #30 first, then address any remaining issues. Done!
Don't forget to update badge in the README

@trevormast trevormast mentioned this issue Jan 26, 2016
Merged
@amoose
Copy link
Member Author

amoose commented Jan 29, 2016

Hakiri needs to be enabled for new org cc @jgrevich

@amoose
Copy link
Member Author

amoose commented Jan 29, 2016

FYI: all critical warnings are squashed by #31 (#30)

@amoose amoose changed the title Address critical security warnings in Hakiri Address critical security warnings in Hakiri / Enable coveralls for new org Jan 29, 2016
@amoose amoose changed the title Address critical security warnings in Hakiri / Enable coveralls for new org Address critical security warnings in Hakiri / Enable Hakiri for new org Jan 30, 2016
@amoose amoose changed the title Address critical security warnings in Hakiri / Enable Hakiri for new org Enable Hakiri for new org Feb 1, 2016
@amoose
Copy link
Member Author

amoose commented Feb 10, 2016

Hakiri is working! 👍 https://hakiri.io/github/fugacious/fugacious/dev

hakiri

@amoose amoose closed this as completed Feb 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jgrevich jgrevich

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jgrevich @amoose