Link to the new stack

[philpotisk]

No description provided.

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

Some or all of your commit messages do not seem to follow the Conventional Commits specification.
To allow the merge of this pull request, we require that at least one commit message or the PR title follow that convention.

You have the following possibilities to proceed with this PR:

1. Make sure at least one commit message complies with the Conventional Commits specification.
   Note, if not all messages comply, the merge will be allowed, but you will still see this warning.
2. Update the title of this pull request to comply with the Conventional Commits specification.

Further information:
The commit messages and PR title will be parsed according to the Conventional Commits specification, to automatically populate the release notes for the next official release.
Therefore, make sure the commit messages or PR title contain the necessary and relevant information describing the changes of this pull request.

Commit message details:

[
  {
    "hash": "621ffc011c5ed6f5b929efc6d2641e2c3d52aa3a",
    "message": "Link to the new stack",
    "valid": false,
    "errors": [
      "subject may not be empty",
      "type may not be empty"
    ],
    "warnings": []
  }
]

PR title details:

No release type found in pull request title "Link to the new stack". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud