Remove unused file current-projects-check.html

[mugdhchauhan]

Prerequisite

1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our Getting Started page.
2. Please make sure you have read our Hack for LA Contributing Guide before you claim/start working on an issue.

Overview

As developers we need to remove the unused file _includes/current-projects-check.html in order to keep the codebase clear and avoid confusion.

Action Items

• Delete the file _includes/current-projects-check.html

Resources/Instructions

• Website page with issue: https://www.hackforla.org/projects-check/
• File on GitHub: https://github.com/hackforla/website/blob/gh-pages/_includes/current-projects-check.html
• Create documentation for projects-check page #3487
• removed unused file current-projects.js #6200
• Remove unused scripts. #6243
• Refactor HTML and JavaScript so Projects and Projects-Check page share same files #5978
• See associated ER for this issue: ER: Unused current-projects-check.html file #7778

[t-will-gillis]

• Please see the notes on ER: Unused current-projects-check.html file #7778
• Previous issues:
  • PR Refactor HTML and JavaScript so Projects and Projects-Check page share same files #5978 fixes Refactor HTML and JavaScript so projects and projects-check pages can share the same files #4960 refactored the "Projects-Check" page to use code from current-projects.html and current-projects.js
  • PR Remove unused scripts. #6243 fixes removed unused file current-projects.js #6200 removed the now-unused current-projects-check.js file
• These issues left current-projects-check.html as an orphan file, which is what is being fixed here

[HackforLABot]

Hi @jmarinit, HfLA appreciates your interest in this issue, but please note that it is in the "New Issue Approval" column of the Project Board because it has not been finalized, approved, or prioritized, and so it is not ready for assignment. For this reason, you have been unassigned from this issue. Please remember to assign issues only from the "Prioritized Backlog" column.

The only exceptions to this rule are if you are writing an issue and the Draft label is applied, or if you are self-assigning to your "Pre-work Checklist" (the issue includes the Complexity: Prework label).