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

First commit for Tkinter GUI #3

Merged
merged 3 commits into from
Aug 27, 2024
Merged

Conversation

mattyjacks
Copy link

I've added gui.py and changed the readme a bit. I've added a Tkinter interface.
image

@mattyjacks
Copy link
Author

Have fun cleaning up my code. It still doesn't automatically handle HTTPS vs HTTP properly.

@NU11Payload NU11Payload self-assigned this Aug 24, 2024
@NU11Payload NU11Payload marked this pull request as draft August 26, 2024 14:51
@NU11Payload NU11Payload marked this pull request as ready for review August 27, 2024 07:52
@NU11Payload NU11Payload merged commit 14e81e2 into NU11Payload:main Aug 27, 2024
1 of 5 checks passed
@NU11Payload
Copy link
Owner

Please keep original contributors. Next time

  • A

@NU11Payload
Copy link
Owner

Commit reverted

Please do not submit Pull request with the branch name of Main.

Instead of using "main" for your feature branches, consider these practices:

  1. Descriptive branch names: Use names that describe the feature or fix you're working on. For example:

    • feature/add-login-page
    • bugfix/resolve-memory-leak
    • hotfix/security-patch-123
  2. Include ticket numbers: If you use an issue tracker, include the ticket number in the branch name:

    • feature/ABC-123-add-user-profile
  3. Use your name or initials: For personal branches, you might include your name:

    • john/refactor-database-queries
  4. Keep the primary branch updated: Regularly merge or rebase the primary branch (usually "main" or "master") into your feature branch to stay up-to-date.

  5. Delete old branches: After a branch is merged, delete it to keep the repository clean.

Moving Forward

Don't worry if this is new to you – we all start somewhere! For your current merge request, you might want to:

  1. Create a new branch with a descriptive name
  2. Cherry-pick or copy your changes to this new branch
  3. Close the current merge request
  4. Open a new merge request from your newly named branch

If you need any help with this process, please don't hesitate to ask. We're here to support you and help you grow as a developer!

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