-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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 issue(s) #265
Comments
@ericdrosado |
@AkashSingh3031 I would recommend creating issues that are specific. The two issues you generated are broad, and might not be appropriate as an Issue. Issues should address a specific problem where someone can work on that problem and then close the issue. An example might be to create an issue seeking contributors to add Let me know if that makes sense or if you would like to brainstorm some ideas. |
Ok, I understand |
@AkashSingh3031 any updates on creating an issue? |
@ericdrosado
it is fine? |
I would recommend instead of using What do you think? |
Yes, this comment seems to be correct. |
Perfect! Closing this issue 👍 |
As the maintainer of a
Collaborate
repo, keeping Issues up-to-date will help the student community understand what they can do to contribute.Perhaps there are interview questions from a certain company you are interested in adding to your repo? I'd recommend generating an issue for that.
In order to submit your project into CX you will need at least one open issue.
The text was updated successfully, but these errors were encountered: