[x] run npm init @adobe/franklin-library or npm init @adobe/franklin-service
[x] Add topics to the repository, at least helix
[x] Add the group "Project Helix Admins" with Admin permissions to the list of collaborators
[ ] Add the group "Project Helix Developers" with Write permissions to the list of collaborators (Project Helix Guests will be taken care of automatically)
[ ] Uncomment and adjust the helix-post-deploy/monitoring command in .github/workflows/main.yaml: decide if your service falls under Development, Publishing or Delivery. (note: failures in the latter two categories will ping on-call engineers on weekends!) See https://www.aemstatus.net for reference.
Create a new service|library repository with the name aem-certificate-provider
Stuff you can do yourself
npm init @adobe/franklin-library
ornpm init @adobe/franklin-service
helix
for services
helix-post-deploy/monitoring
command in.github/workflows/main.yaml
: decide if your service falls under Development, Publishing or Delivery. (note: failures in the latter two categories will ping on-call engineers on weekends!) See https://www.aemstatus.net for reference.Stuff you need an Adobe Org Admin for
for libraries
ADOBE_BOT_NPM_TOKEN
org secret