Skip to content

Epic: Manage CodeQL deployment #5005

Open

Description

@roslynwythe

Overview

We require issues to support resolution of current open CodeQL alerts as well as automation for creation of issues for new CodeQL alerts. We also need to manage CodeQL extraction errors and consider implementing CodeQL for VS Code extension.

Dependencies

Action Items

Resources/Instructions

Footnotes

  1. Code Scanning results for hackforla/website ↩

  2. About code scanning with CodeQL ↩

Activity

  1. added
    role: front endTasks for front end developers
    Feature MissingThis label means that the issue needs to be linked to a precise feature label.
    size: 1ptCan be done in 4-6 hours
    DraftIssue is still in the process of being created
    on Jul 19, 2023
  2. github-actions commented on Jul 19, 2023

    @github-actions
  3. added
    Feature: Refactor JS / LiquidPage is working fine - JS / Liquid needs changes to become consistent with other pages
    and removed
    Feature MissingThis label means that the issue needs to be linked to a precise feature label.
    on Jul 24, 2023
  4. github-actions commented on Jul 24, 2023

    @github-actions
  5. 128 remaining items

  6. HackforLABot commented on Apr 25, 2025

    @HackforLABot
  7. HackforLABot commented on May 2, 2025

    @HackforLABot
  8. HackforLABot commented on May 9, 2025

    @HackforLABot
  9. HackforLABot commented on May 16, 2025

    @HackforLABot
  10. HackforLABot commented on May 22, 2025

    @HackforLABot
  11. HackforLABot commented on May 23, 2025

    @HackforLABot
  12. HackforLABot commented on May 30, 2025

    @HackforLABot
  13. HackforLABot commented on Jun 6, 2025

    @HackforLABot
    Contributor

    @roslynwythe

    Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

    1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
    2. Blockers: "Difficulties or errors encountered."
    3. Availability: "How much time will you have this week to work on this issue?"
    4. ETA: "When do you expect this issue to be completed?"
    5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

    If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

    You are receiving this comment because your last comment was before Tuesday, June 3, 2025 at 12:05 AM PST.

  14. moved this from In progress (actively working) to New Issue Approval in P: HfLA Website: Project Boardon Jun 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions