-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
hangman: implement exercise #745
Comments
can i take up this issue? |
@vaibhavsingh97 of course I suggest creating an empty [WIP] PR - https://github.com/exercism/docs/blob/master/you-can-help/implement-an-exercise-from-specification.md#avoiding-duplicate-work to claim it |
This issue has been automatically marked as |
Hi, I wonder if I can take up this issues as my first contribution for open source? |
@khoa102 Absolutely! Issues can be claimed by creating a PR for them. Please remember to put |
Great! @cmccandless |
Hi, can anyone take a look at the PR for this issue that I submit a few day ago? I would also want to know what should I put for the config of this exercise, like the difficulty, unlock or topic? |
Hey is this issue solved? If not, I'll like to work on it. |
Hi is this issue still relevant? I would like to work on it. Do i need to open an PR to claim it first? |
@junming403 It is still relevant, yes. Also, as stated above:
|
Hi thank you for the prompt response! I have looked at the thread of discussion. Notice it did not use FRP, I am considering make this exercise based on FRP library(http://reactivex.io/intro.html). What should do if the exercise rely on the library? Any guidance? |
RE: the track README
It would be preferable that we stick to that. |
There are exercises that are not yet implemented in Python track (the full list of them - #417 (comment)).
You can help us change this situation by implementing this one. Ref #417
The guide "Implement an exercise from specification" will help you succeed.
If you still have questions, I encourage you to ask them before starting working on the issue.
I also suggest claiming the issue by creating an empty PR as stated here
Please note that there are some special 'closing issue' keywords that you can put in description of your PR and Github will take care of closing the corresponding issue automatically after merge.
This simple thing helps us a lot, and makes our life a bit easier
The text was updated successfully, but these errors were encountered: