PyVerse icon indicating copy to clipboard operation
PyVerse copied to clipboard
Published 3 months ago • verified publisher icon UTSAVS26

Updated Hungman Game

Open shubhagarwal1 opened this issue 1 year ago • 2 comments

Screenshot 2024-10-14 at 11 51 21 PM

Pull Request for PyVerse 💡

Requesting to submit a pull request to the PyVerse repository.

Issue Title

#535 Please enter the title of the issue related to your pull request.

  • [ ] I have provided the issue title.

Info about the Related Issue

What's the goal of the project?
Describe the aim of the project.

  • [ ] I have described the aim of the project.

Name

Please mention your name.
Enter your name here.

  • [ ] I have provided my name.

GitHub ID

Please mention your GitHub ID.
Enter your GitHub ID here.

  • [ ] I have provided my GitHub ID.

Email ID

Please mention your email ID for further communication.
Enter your email ID here.

  • [ ] I have provided my email ID.

Identify Yourself

Mention in which program you are contributing (e.g., WoB, GSSOC, SSOC, SWOC).
Enter your participant role here.

  • [ ] I have mentioned my participant role.

Closes

Enter the issue number that will be closed through this PR.
Closes: #issue-number

  • [ ] I have provided the issue number.

Describe the Add-ons or Changes You've Made

Give a clear description of what you have added or modified.
Describe your changes here.

  • [ ] I have described my changes.

Type of Change

Select the type of change:

  • [ ] Bug fix (non-breaking change which fixes an issue)
  • [ ] New feature (non-breaking change which adds functionality)
  • [ ] Code style update (formatting, local variables)
  • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • [ ] This change requires a documentation update

How Has This Been Tested?

Describe how your changes have been tested.
Describe your testing process here.

  • [ ] I have described my testing process.

Checklist

Please confirm the following:

  • [ ] My code follows the guidelines of this project.
  • [ ] I have performed a self-review of my own code.
  • [ ] I have commented my code, particularly wherever it was hard to understand.
  • [ ] I have made corresponding changes to the documentation.
  • [ ] My changes generate no new warnings.
  • [ ] I have added things that prove my fix is effective or that my feature works.
  • [ ] Any dependent changes have been merged and published in downstream modules.

shubhagarwal1 avatar Oct 14 '24 18:10 shubhagarwal1

👋 Thank you for opening this pull request! We're excited to review your contribution. Please give us a moment, and we'll get back to you shortly!

Feel free to join our community on Discord to discuss more!

github-actions[bot] avatar Oct 14 '24 18:10 github-actions[bot]

fix: #535

Screenshot 2024-10-14 at 11 51 21 PM ## Pull Request for PyVerse 💡 ### Requesting to submit a pull request to the PyVerse repository. #### Issue Title #535 **Please enter the title of the issue related to your pull request.**
  • [ ] I have provided the issue title.

Info about the Related Issue

What's the goal of the project? Describe the aim of the project.

  • [ ] I have described the aim of the project.

Name

Please mention your name. Enter your name here.

  • [ ] I have provided my name.

GitHub ID

Please mention your GitHub ID. Enter your GitHub ID here.

  • [ ] I have provided my GitHub ID.

Email ID

Please mention your email ID for further communication. Enter your email ID here.

  • [ ] I have provided my email ID.

Identify Yourself

Mention in which program you are contributing (e.g., WoB, GSSOC, SSOC, SWOC). Enter your participant role here.

  • [ ] I have mentioned my participant role.

Closes

Enter the issue number that will be closed through this PR. Closes: #issue-number

  • [ ] I have provided the issue number.

Describe the Add-ons or Changes You've Made

Give a clear description of what you have added or modified. Describe your changes here.

  • [ ] I have described my changes.

Type of Change

Select the type of change:

  • [ ] Bug fix (non-breaking change which fixes an issue)
  • [ ] New feature (non-breaking change which adds functionality)
  • [ ] Code style update (formatting, local variables)
  • [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • [ ] This change requires a documentation update

How Has This Been Tested?

Describe how your changes have been tested. Describe your testing process here.

  • [ ] I have described my testing process.

Checklist

Please confirm the following:

  • [ ] My code follows the guidelines of this project.
  • [ ] I have performed a self-review of my own code.
  • [ ] I have commented my code, particularly wherever it was hard to understand.
  • [ ] I have made corresponding changes to the documentation.
  • [ ] My changes generate no new warnings.
  • [ ] I have added things that prove my fix is effective or that my feature works.
  • [ ] Any dependent changes have been merged and published in downstream modules.

shubhagarwal1 avatar Oct 14 '24 22:10 shubhagarwal1

@shubhagarwal1 create a new PR and fill all the details at that time that are asked. When you done it tag me i will merge that pr.

UTSAVS26 avatar Oct 15 '24 03:10 UTSAVS26