Minor tweaks to placeholders fillin

a8cteam51 · Apr 13, 2024 · a823bd7 · a823bd7
1 parent 15302d1
commit a823bd7
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/.github/workflows/fill-in-scaffold.mjs b/.github/workflows/fill-in-scaffold.mjs
@@ -49,7 +49,7 @@ const buildTemplate = async ( filePath ) => {
 		replacements = {
 			'Build Processes Demo': repository.custom_properties['human-title'] ?? repository.name,
 			'A demo project for showcasing standardized build processes for various asset types.': repository.description ?? '',
-			'build-processes-demo-production.mystagingwebsite.com': repository.homepage ?? 'https://wpspecialprojects.com',
+			'https://build-processes-demo-production.mystagingwebsite.com': repository.homepage ?? 'https://wpspecialprojects.com',
 			'build-processes-demo': repository.name,
 			'build_processes_demo': repository.custom_properties['php-globals-long-prefix'],
 			'bpd': repository.custom_properties['php-globals-short-prefix'],

diff --git a/README.scaffold.md b/README.scaffold.md
@@ -18,6 +18,6 @@ NOTE: While PRs are not required to be manually reviewed, we are happy to review
 
 ## Deployment
 
-- Prior to launch, during development, pushing to the `trunk` branch will automatically deploy to the in-progress site at https://EXAMPLE_REPO_PROD_URL
+- Prior to launch, during development, pushing to the `trunk` branch will automatically deploy to the in-progress site at EXAMPLE_REPO_PROD_URL
 - Once this project is launched, pushing to the `trunk` branch will be reviewed and deployed to the production site by a member of the Special Projects Team (see GitHub workflow above)
 - A new dev/staging site will then be created and pushing to the `develop` branch will then automatically deploy that dev/staging site