debug support with `logging.py` module

[H4ppy-04]

About

This feature/enhancement implements changes in the header docstring:
https://github.com/initd1/Cyber-Breach-Detector/blob/f848c272f120feff607256c9f5e95fc6b3667f03/Common/utils.py#L1-L5

• Add an exception in .gitignore that disallows logs from being included in commits
• Move methods that can be converted to functions in ip_reputation_checker.py
• Fix up comments, adding comments where needed and omitting redundant ones. Somewhat pertains to Remove unnecessary comments in the code  #6

[initd1]

Prefer to have the logging changes and the test changes as separate if possible, so the merges can be done separately per issue.

But not too fussy about it for now.

[H4ppy-04]

Prefer to have the logging changes and the test changes as separate if possible, so the merges can be done separately per issue.

But not too fussy about it for now.

• I 100% agree. Apologies for not making the PR's separate. To make the best of the situation, if you can make a separate branch for debug support with logging.py module #21 that extrudes from the current Cyber-Breach-Detector/main branch that would be awesome. I'll separate the changes that I've made in add unit tests and additional necessary omissions #20 into the new branch.

• I also updated the original issue to match the format of the template that you committed in 3bcb77a

• On a separate note, I wanted to let you know that I really like your idea of naming the project Hack-Alert. It has a great ring to it! Would you be open to changing the repository name to match the new project name?

[initd1]

• I 100% agree. Apologies for not making the PR's separate. To make the best of the situation, if you can make a separate branch for debug support with logging.py module #21 that extrudes from the current Cyber-Breach-Detector/main branch that would be awesome. I'll separate the changes that I've made in add unit tests and additional necessary omissions #20 into the new branch.

Please refer to: #23
The new branch created from main has been linked

• I also updated the original issue to match the format of the template that you committed in 3bcb77a

Thanks. Appreciate it.

• On a separate note, I wanted to let you know that I really like your idea of naming the project Hack-Alert. It has a great ring to it! Would you be open to changing the repository name to match the new project name?

Yes! I was intending to do that. Question: Would the repository rename retain the commit history and branches etc?

[H4ppy-04]

Yes! I was intending to do that. Question: Would the repository rename retain the commit history and branches etc?

• Git should automatically manage everything for you, but you'll get a warning saying that the repo name has changed, and it advises you to change that. I believe you can just change the remote url with git remote --set-url <new url>.
• As for retaining the commit history and branches, yes.

[initd1]

Yes! I was intending to do that. Question: Would the repository rename retain the commit history and branches etc?

• Git should automatically manage everything for you, but you'll get a warning saying that the repo name has changed, and it advises you to change that. I believe you can just change the remote url with git remote --set-url <new url>.
• As for retaining the commit history and branches, yes.

thank you. I have renamed the repo to HackAlert. I do intend to rename main.py to hackalert.py, which I will create a new issue for.

Also invited you as a Collaborator. Appreciate your contribution to this repo :)

[H4ppy-04]

Thank you, and I appreciate this honor you've given me. it's been a blast working on this with you.

[H4ppy-04]

• Closed as of PR to merge Logging module to the main branch #25