Repository navigation
Epic: Manage CodeQL deployment #5005
Copy link
Copy link
Open
Labels
Complexity: See issue making labelSee the Issue Making label to understand the issue writing difficulty levelSee the Issue Making label to understand the issue writing difficulty levelFeature: Code AlertsIssue Making: Level 2Make issue(s) from an ER or EpicMake issue(s) from an ER or Epicrole: back end/devOpsTasks for back-end developersTasks for back-end developersrole: front endTasks for front end developersTasks for front end developerssize: 2ptCan be done in 7-12 hoursCan be done in 7-12 hours
Milestone
Description
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
- Create new issue template for resolution of CodeQL alert #5242
- Create wiki page to guide developers how to manage CodeQL alerts #6463
- Create issues to resolve all open CodeQL alerts #5159
- Create GHA to create issues when new CodeQL alerts are detected #5059
- Resolve CodeQL extraction errors #5234
- Update codeql.yml to exclude YAML front-matter and Liquid code #6548
- Feasibility and DR: use of CodeQL for VS Code #5180
- Refactor codeql.yml file #6691
Action Items
- View the code scanning page1 for hackforla/website, and understand the elements of CodeQL code scanning2
- Create issue template Create new issue template for resolution of CodeQL alert #5242
- Create a sample issue - Resolve CodeQL alert 25 #5642
- Create a level 1 issue making issue with a list of required issues - see Create issues to resolve all open CodeQL alerts #5159
- Create an issue for creation of a wiki page "How to manage CodeQL alerts" - Create wiki page to guide developers how to manage CodeQL alerts #6463
- fix link from Action Item to alert
- set role label based on path of affected code file
- if path starts with
.githuborgithub-actions=> apply `role: back end/devOps - otherwise apply
role: front endlabel
- if path starts with
- determine if the code file is in production
- for pages, check YAML front matter for
published: - for layouts, check
_config.yml
- for pages, check YAML front matter for
Resources/Instructions
- This Epic was created from ER: Analyze CodeQL security/code quality alerts #4963
Footnotes
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Complexity: See issue making labelSee the Issue Making label to understand the issue writing difficulty levelSee the Issue Making label to understand the issue writing difficulty levelFeature: Code AlertsIssue Making: Level 2Make issue(s) from an ER or EpicMake issue(s) from an ER or Epicrole: back end/devOpsTasks for back-end developersTasks for back-end developersrole: front endTasks for front end developersTasks for front end developerssize: 2ptCan be done in 7-12 hoursCan be done in 7-12 hours
Type
Projects
- StatusShow more project fieldsNew Issue Approval
Activity
github-actions commentedon Jul 19, 2023
github-actions commentedon Jul 24, 2023
128 remaining items
HackforLABot commentedon Apr 25, 2025
HackforLABot commentedon May 2, 2025
HackforLABot commentedon May 9, 2025
HackforLABot commentedon May 16, 2025
HackforLABot commentedon May 22, 2025
HackforLABot commentedon May 23, 2025
HackforLABot commentedon May 30, 2025
HackforLABot commentedon Jun 6, 2025
@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.
If you need help, be sure to either: 1) place your issue in the
Questions/In Reviewcolumn 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.