- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 777
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Epic: Enable code scanning on JS files #6378
Labels
Complexity: Large
Complexity: See issue making label
See the Issue Making label to understand the issue writing difficulty level
Dependency
An issue is blocking the completion or starting of another issue
epic
Feature: Code Alerts
Feature: Refactor JS / Liquid
Page is working fine - JS / Liquid needs changes to become consistent with other pages
Issue Making: Level 2
Make issue(s) from an ER or Epic
role: back end/devOps
Tasks for back-end developers
role: front end
Tasks for front end developers
size: 1pt
Can be done in 4-6 hours
Milestone
Comments
roslynwythe
added
Feature Missing
This label means that the issue needs to be linked to a precise feature label.
size: missing
epic
Draft
Issue is still in the process of being created
role missing
Complexity: Missing
labels
Feb 26, 2024
This comment was marked as outdated.
This comment was marked as outdated.
roslynwythe
added
Feature: Refactor JS / Liquid
Page is working fine - JS / Liquid needs changes to become consistent with other pages
Feature: Code Alerts
role: front end
Tasks for front end developers
role: back end/devOps
Tasks for back-end developers
and removed
Feature Missing
This label means that the issue needs to be linked to a precise feature label.
role missing
labels
Feb 26, 2024
This was referenced Feb 26, 2024
roslynwythe
added
Complexity: See issue making label
See the Issue Making label to understand the issue writing difficulty level
Issue Making: Level 2
Make issue(s) from an ER or Epic
Complexity: Medium
size: 1pt
Can be done in 4-6 hours
Ready for Prioritization
ready for product
and removed
size: missing
Complexity: Missing
Draft
Issue is still in the process of being created
Ready for Prioritization
labels
Feb 28, 2024
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
ExperimentsInHonesty
added
ready for dev lead
Issues that tech leads or merge team members need to follow up on
and removed
ready for product
labels
Mar 3, 2024
ExperimentsInHonesty
added
the
ready for dev lead
Issues that tech leads or merge team members need to follow up on
label
Mar 8, 2024
This comment was marked as outdated.
This comment was marked as outdated.
roslynwythe
added
Ready for Prioritization
and removed
ready for dev lead
Issues that tech leads or merge team members need to follow up on
labels
Mar 11, 2024
This comment was marked as outdated.
This comment was marked as outdated.
5 tasks
gaylem
added
the
Dependency
An issue is blocking the completion or starting of another issue
label
Mar 29, 2024
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
@roslynwythe Sorry, I should have asked you about this one when we were online today.
|
ExperimentsInHonesty
added
ready for dev lead
Issues that tech leads or merge team members need to follow up on
and removed
ready for product
labels
Apr 24, 2024
|
roslynwythe
added
ready for product
and removed
ready for dev lead
Issues that tech leads or merge team members need to follow up on
labels
Apr 28, 2024
I have removed the ready for labels... and when the dependency is satisfied, this issue will get looked at again by the merge team in the new issue approval column |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Complexity: Large
Complexity: See issue making label
See the Issue Making label to understand the issue writing difficulty level
Dependency
An issue is blocking the completion or starting of another issue
epic
Feature: Code Alerts
Feature: Refactor JS / Liquid
Page is working fine - JS / Liquid needs changes to become consistent with other pages
Issue Making: Level 2
Make issue(s) from an ER or Epic
role: back end/devOps
Tasks for back-end developers
role: front end
Tasks for front end developers
size: 1pt
Can be done in 4-6 hours
Dependency
Overview
Explore options to enable scanning, including the option of modifying the Javascript code to eliminate non-JS statements, as well as the option of performing CodeQL scanning after the Jekyll build.
Details
Many of our Javascript code files cannot be scanned by CodeQL as-is because they contain non-JS (liquid) code which cause extraction errors.
Summary: Non-JS code in these files
hamburger-nav.js
: YAML front-matter with a titletoolkit.js
: 1 line of Liquid, empty YAML front-matterwins.js
: 2 lines (Liquid), empty YAML front-matterproject.js
: 2 lines (Liquid), empty YAML front-matterabout.js
: for loop (Liquid), empty YAML front-mattercurrent-project.js
: 2 lines + for loop (Liquid), empty YAML front-matterAction Items
The text was updated successfully, but these errors were encountered: