GGIRCS: As a maintainer, I want my repository to expose a BCGov Public Code file, so that I can make my work discoverable by the wider government

[pbastia]

Description:

The info feeds into a dashboard view of all open source gov't applications, showing tech stacks, hosting, common components, and other key info at a glance. It's an easy way to see what other teams/applications are on the same tech stack/using the same components.

Acceptance Criteria:

Given I am a developer When I visit the cas-ggircs repository Then there is a bcgovpubcode.yml at the root of the repository And that file contains up-to-date information

Development Checklist:

• [ ] generate the file here: https://pubcode.apps.silver.devops.gov.bc.ca/
• [ ] Checklist item
• [ ] Checklist item
• [ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

• [ ] User story is included
• [ ] User role and type are identified
• [ ] Acceptance criteria are included
• [ ] Wireframes are included (if required)
• [ ] Design / Solution is accepted by Product Owner
• [ ] Dependencies are identified (technical, business, regulatory/policy)
• [ ] Story has been estimated (under 13 pts)

·Definition of Done (Note: If any of these points are not applicable, mark N/A)

• [ ] Acceptance criteria are tested by the CI pipeline
• [ ] UI meets accessibility requirements
• [ ] Configuration changes are documented, documentation and designs are updated
• [ ] Passes code peer-review
• [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
• [ ] Ticket is ready to be merged to main branch
• [ ] Can be demoed in Sprint Review
• [ ] Bugs or future work cards are identified and created
• [ ] Reviewed and approved by Product Owner

Notes:

-

[patriciarussellCAS]

Will we need to do this before we sunset GGIRCS, or can this type of work be done later once our new system is set up? Adding to our data warehouse epic in case it's relevant for that work.