-
Notifications
You must be signed in to change notification settings - Fork 56
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
Add something indicating we use zenhub to help manage issues #110
Comments
Link here: https://www.zenhub.io/ |
I would say README under the contributing section. I actually haven't been using zenhub, but I've been meaning to look at it. Slightly related to #109 |
For some of my projects I link to a contribution guide that sits in the wiki. EX: https://github.com/codeforsanjose/codeforsanjose-backend/wiki/Contribution-Guide |
👍 to adding a contribution guide |
revisiting this so that we can move on some of these items, or close them out. now that we are trying this "projects" tab, how does that affect this idea of including info about zenhub? @jasonlally @jszwedko @jafowler49 |
I'd say that the Projects tab takes the place of what we would have used Zenhub for (and is documented in https://github.com/sfbrigade/adopt-a-drain/wiki/Adopt-a-Drain-SF-Development-and-Deployment-Processes). I'm 👍 on closing this one. |
ditto @jszwedko |
another one bites the dust. thanks @jafowler49 and @jszwedko! |
I don't know where to put it, maybe just the Readme? But zenhub needs to be installed as a browser extension in order for the boards to be visible. This may help new folks get plugged into where things are.
The text was updated successfully, but these errors were encountered: