-
Notifications
You must be signed in to change notification settings - Fork 207
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
infopanel: render scenario_description as markdown #5374
infopanel: render scenario_description as markdown #5374
Conversation
44ab702
to
17f2445
Compare
17f2445
to
acf9c7f
Compare
Try it with:
AFAIK, this change might also affect the view of scenario descriptions used in Testsuites #1094. But I think using Markdown here as well, is a benefit. WDYT? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now only CI checks need to be fixed
Are these failures related to my changes? I didn't connect
and with https://build.opensuse.org/package/show/devel:openQA:GitHub:os-autoinst:openQA:PR-5374/openQA
I'm not sure where this comes from. Maybe you can give me a hint how to fix it? |
None of these failures seem related. The cache creation might be fixed by ensuring your commit is based on the latest commit from the master branch. The checks on OBS also look like something we've already been fixed so the same applies here. |
I would like to have clickable links in the JOB_DESCRIPTION. With this, I could use the JOB_DESCRIPTION linking to a corresponding trigger source (e.g. a gitlab pipeline).
acf9c7f
to
d411e9c
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5374 +/- ##
=======================================
Coverage 98.36% 98.36%
=======================================
Files 389 389
Lines 37441 37445 +4
=======================================
+ Hits 36827 36831 +4
Misses 614 614 ☔ View full report in Codecov by Sentry. |
I would like to have clickable links in the
JOB_DESCRIPTION
. With this, I could use theJOB_DESCRIPTION
linking to a corresponding trigger source (e.g. a gitlab pipeline).