chore: preview branch output inside description instead of comment

[nmerget]

Proposed changes

Add a preview URL only if the deployment was successful instead of adding a comment on opening the PR

Types of changes

• Bugfix (non-breaking change that fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactoring (improvements to existing components or architectural decisions)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Further comments

🔭🐙🐈 Test this branch here: https://db-ux-design-system.github.io/core-web/review/chore-preview-url

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3572c94

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[mfranzke]

@nmerget As I understand it, the URL would be added to or replaced in the description after a successful deployment in each pipeline run. However, it wouldn't change over time because it's a consistent name. What would be the benefit of changing the current simple implementation to this more extended one, besides the timing of adding it after a successful deployment, and not already upfront? Our pages are always deployed to that URL, and if I want to ensure I get the latest deployment, I need to check the latest commit's green pipeline status anyhow.

(I'm not questioning the decision to move the URL from the comment to the PR description.)

[nmerget]

@nmerget As I understand it, the URL would be added to or replaced in the description after a successful deployment in each pipeline run. However, it wouldn't change over time because it's a consistent name. What would be the benefit of changing the current simple implementation to this more extended one, besides the timing of adding it after a successful deployment, and not already upfront? Our pages are always deployed to that URL, and if I want to ensure I get the latest deployment, I need to check the latest commit's green pipeline status anyhow.

(I'm not questioning the decision to move the URL from the comment to the PR description.)

Yes you are right, I think it is confusing to have a comment with a link which isn't available.