-
Notifications
You must be signed in to change notification settings - Fork 24
Manually add pagerduty
workspace to commit d8dc915
for backstage 1.40.0
on branch main
#1556
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
Conversation
/publish |
Publish workflow has completed with failure. |
…`1.40.0` on branch `main` Signed-off-by: David Festal <[email protected]>
391756d
to
dde137f
Compare
/publish |
Publish workflow has completed with failure. |
/publish |
Publish workflow has completed with failure. |
/publish |
Publish workflow has completed with failure. |
/publish |
Publish workflow has completed with failure.
|
Signed-off-by: David Festal <[email protected]>
9545019
to
31e5980
Compare
/publish |
Signed-off-by: David Festal <[email protected]>
Publish workflow has completed with failure. |
/publish |
Publish workflow has completed with success.
|
Add the corresponding metadata files to enable testing for this workspace. |
Manually add pagerduty workspace at commit PagerDuty/backstage-plugins@d8dc915 for backstage
1.40.0
on branchmain
.This PR was created manually.
This proposal is a Best-Effort Backstage compatibility match. Plugin sources are built for Backstage
1.41.1
. Please review and test before merging.If you have tested and confirmed compatibility, you should add a
backstage.json
file in the workspace folder to override the known Backstage compatibility to be the target Backstage version.Don't forget to also update the
repo-backstage-version
field insource.json
accordingly.This proposal is a Best-Effort Backstage compatibility match. Plugin sources are built for Backstage
1.41.1
. Please review and test before merging.If you have tested and confirmed compatibility, you should add a
backstage.json
file in the workspace folder to override the known Backstage compatibility to be the target Backstage version.Don't forget to also update the
repo-backstage-version
field insource.json
accordingly.You might need to complete it with additional dynamic plugin export information, like:
app-config.dynamic.yaml
file for frontend plugins,scalprum-config.json
file for frontend plugins,patches/
directoryBefore merging, you need to export the workspace dynamic plugins as OCI images,
and if possible test them inside a RHDH instance.
To do so, you can use the
/publish
instruction in a PR review comment.This will start a PR check workflow to: