You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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 .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.
Create a new library repository with the name
helix-universal-devserver
Stuff you can do yourself
npm init @adobe/helix-library
ornpm init @adobe/helix-service
helix
for services
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.CIRCLECI_TOKEN
to the repository secrets.Stuff you need an Adobe Org Admin for
for libraries
ADOBE_BOT_NPM_TOKEN
org secretThe text was updated successfully, but these errors were encountered: