Create a new library repository with the name helix-universal-devserver
Stuff you can do yourself
[ ] run npm init @adobe/helix-library or npm init @adobe/helix-service
[ ] Add topics to the repository, at least helix
[x] Add the group "Project Helix Admins" with Admin permissions to the list of collaborators
[x] 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 .circleci/config.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://status.project-helix.io for reference.
[ ] Add a CIRCLECI_TOKEN to the repository secrets.
Create a new library repository with the name
helix-universal-devserverStuff you can do yourself
npm init @adobe/helix-libraryornpm init @adobe/helix-servicehelixfor services
helix-post-deploy/monitoringcommand in.circleci/config.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://status.project-helix.io for reference.CIRCLECI_TOKENto the repository secrets.Stuff you need an Adobe Org Admin for
for libraries
ADOBE_BOT_NPM_TOKENorg secret