MAGREQ-9001::Add metadata file to active repos

[glo82145]

Description

Overview
All Commerce engineering teams are being asked to add a new metadata file to all their active repositories. Kodiak team has committed to using this metadata file to make connections between repos, products, and teams. This small update will make following up on breaches, vulnerabilities, or ticket-able Kodiak findings much easier.

Creating the metadata file
In the default branch of your repo, create folder .github and add to it a file named .metadata.json.
Use the sample content below as a template to provide the necessary information.

{
"templateVersion": "0.2",
"product": {
"name": "Page Builder",
"description": "Content creation module for Magento",
},
"contacts": {
"team": {
"name": "Obesessive Owls",
"DL": "Grp-obsessive-owls-team", # this should not contain email, only DL names
"slackChannel": "#slack-channel"
}
},
"ticketTracker": {
"functionalJiraQueue": {
"projectKey": "PKGS",
"component": "
},
"securityJiraQueue": {
"projectKey": "MAGREQ",
"component": "MAGREQ/PageBuilder"
}
},
"productionCodeBranches": ["main"]
}
Create a PR to the default branch of your repo, making sure to link back to this ticket.

More detailed instructions can be found here: Onboarding for Teams

Which repos to update?
A metadata file should be created and added to all active repos belonging to your team. This includes public and private repos.

Related Issue

Closes https://jira.corp.adobe.com/browse/MAGREQ-9001

Acceptance

Verification Stakeholders

Specification

Verification Steps

Test scenario(s) for direct fix/feature

Test scenario(s) for any existing impacted features/areas

Test scenario(s) for any Magento Backend Supported Configurations

Is Browser/Device testing needed?

Any ad-hoc/edge case scenarios that need to be considered?

Screenshots / Screen Captures (if appropriate)

Breaking Changes (if any)

Checklist

• I have added tests to cover my changes, if necessary.
• I have added translations for new strings, if necessary.
• I have updated the documentation accordingly, if necessary.

[pwa-studio-bot]

	Fails
🚫	A version label is required. A maintainer must add one.

	Messages
📖	Associated JIRA tickets: MAGREQ-9001.
📖	DangerCI Failures related to missing labels/description/linked issues/etc will persist until the next push or next pr-test build run (assuming they are fixed).
📖	Access a deployed version of this PR here. Make sure to wait for the "pwa-pull-request-deploy" job to complete.

Generated by 🚫 dangerJS against 082be5a