Tickets Availability Checking and Booking Alert

[DEEKSHACodeaim]

Description

This is a new script that scrapes book my show for the show details from the website based on the details of the show like movie name, city, date, and venue details, and send an email alert when the ticket is available

Fixes #2182

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Documentation Update

Checklist:

• My code follows the style guidelines(Clean Code) of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have created a helpful and easy to understand README.md
• My documentation follows Template for README.md
• I have added the project meta data in the PR template.
• I have created the requirements.txt file if needed.

Project Metadata

If there is no-file/nothing to fill the below fields with, then type: none

Example: If no requirements.txt needed/present, then type none in Requirments.

Category:

• Calculators
• AI/ML
• Scrappers
• Social_Media
• PDF
• Image_Processing
• Video_Processing
• Games
• Networking
• OS_Utilities
• Automation
• Cryptography
• Computer_Vision
• Fun
• Others

Title: MOVIE TICKET BOOKING ALERT AUTOMATION

Folder: Ticket Booking Alert

Requirements: Python3

Script: ticket-book-alert.py

Arguments: None

Contributor: DEEKSHACodeaim

Description:Check the website "Book My Show" for the required tickets and sends an alert email when tickets are available. Enter the custom details as required in the '<>' inside the script and run the script

[DEEKSHACodeaim]

@avinashkranjan, hope you like the idea of my script and merge my PR.

[gitguardian]

⚠️ GitGuardian has uncovered 5 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	Secret	Commit	Filename
-	Company Email Password	7351e9e	Ticket Booking Alert/ticket-book-alert.py	View secret
-	Company Email Password	db75229	Ticket Booking Alert/ticket-book-alert.py	View secret
-	Generic Password	75f1f03	Ticket Booking Alert/ticket-book-alert.py	View secret
-	Generic Password	b0b87d4	Ticket Booking Alert/ticket-book-alert.py	View secret
-	Generic Password	b0b87d4	Ticket Booking Alert/ticket-book-alert.py	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[DEEKSHACodeaim]

@avinashkranjan, please consider this PR

[github-actions]

Due to inactivity this pull request has been marked as stale.

[DEEKSHACodeaim]

hey @avinashkranjan there is a github workflow action that needs to be fixed, since I have forked from this repo, Im constantly bugged with this warning everyday - " assign_issues
Unhandled error: TypeError: Cannot read properties of undefined (reading 'number')
assign_issues
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/github-script@v4. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/"
Can you please look into it and fix it?
Thankyou