Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added stage-type badges to teletraan environments page #1707

Merged
merged 1 commit into from
Sep 4, 2024

Conversation

bhnord
Copy link
Contributor

@bhnord bhnord commented Sep 3, 2024

canary:

  • canary badge

control:

  • control badge

dev:

  • dev badge

latest:

  • latest badge

production:

  • production badge

staging:

  • staging badge

@bhnord bhnord requested a review from a team as a code owner September 3, 2024 16:10
@github-actions github-actions bot added the deploy-board Includes changes to deploy-board label Sep 3, 2024
@@ -372,6 +372,9 @@ <h4 class="panel-title pull-left pointer-cursor">
</div>
{% endif %}
{% endif %}
<h6 class="stage-type-badge">
{{env.stageType|default:"NO STAGE TYPE"}}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added NO STAGE TYPE as stageType is an optional field from the API according to the docs

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm thinking we could show a warning if the stage type is missing, to encourage users to set it. The warning could be similar to the one in the screenshot.

However, I think we could discuss this separately, so this change looks good to me 👍

@bhnord bhnord merged commit 474a58e into master Sep 4, 2024
6 checks passed
@bhnord bhnord deleted the bnordemann/ui-stage-type-badge branch September 4, 2024 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deploy-board Includes changes to deploy-board
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants