Skip to content

Epic: Create template, spreadsheet and list of issues for quotations usage audit #8856

Open

Description

@anthonylo87

Dependency (Small issues)

  • [ ]

Overview

We need to create issues to audit all codebase MD/YML files for the appropriate usage of quotations, in line with the recommendation on best practices outlined in #7540. The HfLA quotation audit spreadsheet (to be created) will be used to track quotation audit issues, record false positives, and track resulting issues for resolving errors.

More Details

Our Markdown and YAML files should contain single quotes only around strings containing special characters or other data types i.e. numbers or Booleans that we want to treat as strings. This will involve removing some existing unnecessary quotes and possibly changing some double quotes to single.

We need to create an Epic issue to audit the .md and .yml files in our codebase for the following:

  • Unnecessary quotes
  • Double quotes
  • Missing quotes (in particular, some URLs with colons are missing quotes)

Action Items

  • Create HfLA quotation audit spreadsheet (and include link as a resource below)
    • List files we wish to check quotation usage for in Page Audit sheet
    • List excluded files/paths in Excluded Paths sheet - Some files may be excluded from the audit if they use Markdown only for formatting, e.g. CONTRIBUTING.md and GHA comment templates.
    • Create an additional sheet for auditors to fill in results. Columns will include the file path, the code snippet containing quotes, a true/false selector for indicating whether the quote is necessary, and a note column to provide more information
  • In a comment on this issue, draft an issue template for checking quotation usage in an individual file (Small)
    • Write some sample cases of variables that should and should not be in quotes to include or link in the template
    • Create an issue to make the template - Link here when created
  • In a comment on this issue, draft an issue template for an Issue Making Level 1 issue to create a batch of issues to check individual files
    • Create an issue to make the template - Link here when created
  • Create Issue Making Level 1 issues (used to to create individual issues) and list this issue as the parent
  • Generate small issues and list above in dependency section

Resources/Instructions

Activity

  1. github-actions commented on Oct 27, 2026

    @github-actions
  2. added this to the 08. Team workflow milestone on Oct 28, 2026
  3. added
    ready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritization
    non-PR contributionFor wiki additions/revisions, audit spreadsheet contributions, issue-making ERs and Epics, etc.
    on Oct 28, 2026
  4. added and removed
    ready for merge teamneeds a senior review either to do some re writing or to approve it for ready for prioritization
    on Oct 30, 2026
  5. moved this from New Issue Approval to Ready for Prioritization in P: HfLA Website: Project Boardon Nov 1, 2026
  6. meghan-oconnell commented on Nov 3, 2026

    @meghan-oconnell
    Member

    @anthonylo87 Thank you for working on this Epic. It's looking good, I've gone ahead and moved it along to ready for Prioritization. Though, it could use a bit more clarity around the Action items, specifically the ones on making templates. It could be helpful to add links to supporting documentation and example issues for reference.

    If it helps, here are some resources for template making:

    When you get he chance, can you add that extra conext?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions