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.

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

Morse Code Translator with GUI #26

Closed
wants to merge 0 commits into from

Conversation

aviralgarg05
Copy link
Contributor

Pull Request for PyVerse 💡

Issue Title : Morse Code Translator with GUI

  • Info about the related issue (Aim of the project) : Morse Code Translator with GUI
  • Name: Aviral Garg
  • GitHub ID: aviralgarg05
  • Email ID: [email protected]
  • Idenitfy yourself: (Mention in which program you are contributing in. Eg. For a WoB 2024 participant it's, WoB Participant) GSSOC'24 Extended

Closes: #issue number that will be closed through this PR
#9

Describe the add-ons or changes you've made 📃

Morse Code Translator with GUI
Give a clear description of what have you added or modifications made
Morse Code Translator with GUI using Tkinter Interface and translation algorithms

Type of change ☑️

What sort of change have you made:

  • 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 it has been tested: - Correct Outputs
Describe how have you verified the changes made: - Various available Morse Code translators on web

Checklist: ☑️

  • 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.

Copy link

github-actions bot commented Oct 2, 2024

👋 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!

@github-actions github-actions bot requested a review from UTSAVS26 October 2, 2024 11:27
Copy link
Owner

@UTSAVS26 UTSAVS26 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please update your README file based on this template and please sync your fork before adding the code otherwise it can cause problem

@aviralgarg05
Copy link
Contributor Author

I will recreate the pr, probably both the commits were made at the same time, so my fork couldnt get synced

@UTSAVS26
Copy link
Owner

UTSAVS26 commented Oct 2, 2024

I will recreate the pr, probably both the commits were made at the same time, so my fork couldnt get synced

For future, remember to sync the fork before commiting your code. It's a good practice. All the best

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants