Version 1.0 (Console App) of Football Match Predictor

[N-Endy]

Later versions of the program will implement Machine Learning to predict matches. It will also be converted from a console app to a web app

[TheCSharpAcademy]

@N-Endy I'm really sorry it took so long to review this project. I lost visibility over it on my dashboard due to a bug. Would you still like m eto review it? If so... does it still work for you? I'm getting this:

[N-Endy]

Hello Pablo, It's nice to get a message from you. Yes, I would still like it reviewed, as it would give insight into things I need to work on. However, I have upgraded the project from a console app to a FullStack project using Razor Pages. I will update the repo. Thank you. Regards

…

On Thu, Sep 25, 2025 at 5:48 AM The C# Academy ***@***.***> wrote: ***@***.**** requested changes on this pull request. @N-Endy <https://github.com/N-Endy> I'm really sorry it took so long to review this project. I lost visibility over it on my dashboard due to a bug. Would you still like m eto review it? If so... does it still work for you? I'm getting this: image.png (view on web) <https://github.com/user-attachments/assets/d5200332-2260-4d7e-840b-5bec4095e99f> — Reply to this email directly, view it on GitHub <#3 (review)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AM3CH7RVFAY5VIE5MVSM7SD3UNXZFAVCNFSM6AAAAACHOFTEFKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTENRVGY3TMNRSGY> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>

[gitguardian]

⚠️ GitGuardian has uncovered 2 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.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	ODBC Connection String	d19b6da	MatchPredictor/MatchPredictor.Web/appsettings.Production.json	View secret
-	-	ODBC Connection String	d19b6da	MatchPredictor/MatchPredictor.Web/appsettings.Development.json	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.

---

^{🦉 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.}