Use as an example https://github.com/drevops/docker-wait-for-dependencies/blob/main/.github/workflows/release.yml

When running init.sh script with different options selected, there are different types of string replacements take place.

This issue is to conduct a limited 2 hrs testing to document all possible issues with replacements as new issues.

It may appear that we need to ask user for more inputs in init.sh script - document this as well.

SDs

Run ./init.sh with different variants and check what string have and have not been replaced. For example, currently the namespace in the PHP tests is not replaced.

Copy from https://github.com/AlexSkrypnyk/box-release-example and archive that repo

We have been using Just the docs, but it is a bit limited and uses Ruby which makes it a bit hard to maintain and understand.

https://docusaurus.io/ looks like a good replacement and it is written in JS.

Also, add #!/usr/bin/env php

1. Updated the rector.php config as per https://github.com/drevops/scaffold/blob/develop/rector.php#L53
2. Update current example PHP code to contain declare(strict_types=1);.
3. Check if Coder rules in phpcs.xml pick up the missing declare(strict_types=1);. If so - find a package that enforces this rule and add it as a dev dependency to composer.json.

Add a linter for github actions yaml files to enforce the format:

1. Yaml format - check for overall syntax
2. Actions format - check for semantic syntax
3. Style format - enforce a specific format around the structure (but make it configurable):

• name must be present

This functionality should be shipped with the scaffolded projects to enforce checks for their GHA configs.

Running large test suites with XDebug coverage driver has shown a significant CI slowdown on large projects.

We need to consider using pcov instead.

Update the GHA step to only run if the secrets.CODECOV_TOKEN provided.

Current GH action is good, but it does not provide a quick way to look at the current coverage (the badge is not link to an HTML report).

We need to either update the badge to point to the HTML asset from the build or switch to Codecov

init.sh does not replace a namespace in the PHP tests.

also, .gitatributes does not contain:

• phpcs.xml
• phpmd.xml
• phpstan.neon
• phpunit.xml

php-script.php instead of php-script in:

• phpstan.neon
• phpcs.xml

reactphp/promise#252

composer/composer#11620

2023-09-09T06:24:03.9342445Z   - Installing humbug/box (4.3.8): Extracting archive
2023-09-09T06:24:04.0777833Z     Install of symfony/var-dumper failed
2023-09-09T06:24:04.1830005Z     Install of seld/jsonlint failed
2023-09-09T06:24:04.3146223Z     Install of justinrainbow/json-schema failed
2023-09-09T06:24:04.3229868Z     Install of humbug/php-scoper failed
2023-09-09T06:24:04.3329068Z     Skipped installation of bin bin/php-parse for package nikic/php-parser: name conflicts with an existing file
2023-09-09T06:24:04.5199032Z     Install of humbug/box failed
2023-09-09T06:24:04.5224281Z Unhandled promise rejection with ArgumentCountError: Too few arguments to function React\Promise\Promise::React\Promise\{closure}(), 0 passed in phar:///usr/bin/composer/src/Composer/Installer/InstallationManager.php on line 660 and exactly 1 expected in phar:///usr/bin/composer/vendor/react/promise/src/Promise.php:277
2023-09-09T06:24:04.5227758Z Stack trace:
2023-09-09T06:24:04.5228456Z #0 phar:///usr/bin/composer/src/Composer/Installer/InstallationManager.php(660): React\Promise\Promise::React\Promise\{closure}()
2023-09-09T06:24:04.5229368Z #1 phar:///usr/bin/composer/vendor/react/promise/src/Internal/FulfilledPromise.php(47): Composer\Installer\InstallationManager::Composer\Installer\{closure}()
2023-09-09T06:24:04.5233862Z #2 phar:///usr/bin/composer/src/Composer/Installer/InstallationManager.php(661): React\Promise\Internal\FulfilledPromise->then()
2023-09-09T06:24:04.5252804Z #3 phar:///usr/bin/composer/vendor/react/promise/src/Promise.php(288): Composer\Installer\InstallationManager::Composer\Installer\{closure}()
2023-09-09T06:24:04.5253920Z #4 phar:///usr/bin/composer/vendor/react/promise/src/Promise.php(37): React\Promise\Promise->call()
2023-09-09T06:24:04.5254734Z #5 phar:///usr/bin/composer/src/Composer/Installer/InstallationManager.php(663): React\Promise\Promise->__construct()
2023-09-09T06:24:04.5255617Z #6 phar:///usr/bin/composer/src/Composer/Installer/InstallationManager.php(221): Composer\Installer\InstallationManager->runCleanup()
2023-09-09T06:24:04.5256466Z #7 phar:///usr/bin/composer/src/Composer/Installer.php(791): Composer\Installer\InstallationManager->execute()
2023-09-09T06:24:04.5257175Z #8 phar:///usr/bin/composer/src/Composer/Installer.php(616): Composer\Installer->doInstall()
2023-09-09T06:24:04.5257866Z #9 phar:///usr/bin/composer/src/Composer/Installer.php(290): Composer\Installer->doUpdate()
2023-09-09T06:24:04.5258585Z #10 phar:///usr/bin/composer/src/Composer/Command/RequireCommand.php(490): Composer\Installer->run()
2023-09-09T06:24:04.5259366Z #11 phar:///usr/bin/composer/src/Composer/Command/RequireCommand.php(339): Composer\Command\RequireCommand->doUpdate()
2023-09-09T06:24:04.5260178Z #12 

https://github.com/tj/commander.js

Also, add CI and publishing workflow.

Test helpers should not be a part of test coverage as any changes to test helpers will affect the coverage of the SUT and will lead to false-positives.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

PHP 8.4 will be released in 2024

We need to add support for 8.4

neither dir nor workflow action

this is to make sure that docs can be browsed in GitHub

PHP 8.1 has security support till 25 Nov 2024

We need to remove support for 8.1

Y is treated as n instead of y

copy from https://github.com/AlexSkrypnyk/bats-example and include test code coverage

add tests similar to https://github.com/AlexSkrypnyk/drupal-module-renamer/blob/main/.github/workflows/test.yml

When managing multiple repositories, there is a significant effort required to setup configuration of the Github repos. While org-wide repo settings exist, personal repos do not have those settings available.

Need to find a solution that will be using some sort of config file to control the repo settings.

Similar to https://github.com/drevops/drevops/blob/develop/scripts/drevops/github-labels.sh, we need to have a quick way to configure a GitHub repo using a script.

The script should handle:

• General settings
• Labels
• Protected branches

Currently, only command is setup to be published.

<img width=200px height=200px src="https://placehold.jp/000000/ffffff/200x200.png?text=Project&css=%7B%22border-radius%22%3A%22%20100px%22%7D" alt="Project logo"></a>

that will look like

Use [verb]-[noun].yml format.

For example, release-notes.yml or publish-docs.yml

Also, update the names of the jobs and names of the actions.

The trigger conditions should not be a part of the name.

This is useful to allow commands to have documented options.

See https://github.com/AlexSkrypnyk/shellvar for reference

Add

"config": {
    "sort-packages": true
}

https://github.com/release-drafter/release-drafter#version-resolver

But set default to be minor rather than patch

Docs spelling does not exclude code

Also, the mdx is not recognised as markdown.

add to cspel.json:

"overrides": [
        {
            "filename": "**/*.mdx",
            "languageId": [
                "mdx",
                "markdown"
            ]
        }
    ],
    "languageSettings": [
        {
            "languageId": "markdown",
            "ignoreRegExpList": [
                "/^\\s*```(.|\\n)+?^\\s*```/gm"
            ]
        }
    ]

/docs
/tests

The logo placeholder generator sometimes has outages, which leads to rendering the logo image as a broken link, making the repo look bad.

Suggestion here is to generate the logo file, attach it to the onboarding ticket and replace it in the README.md file.

So would need to add one more step to the onboarding instructions.