Himanshu Mishra

Thanks for pointing it out Sanket. This ambiguity should not be present.

+1, this solved my problem as well.

@yashrsharma44 We need to use templates, yes. The current website was developed way in the past (when we didn't know how to create websites) :D We can use any static...

This is amazing! Thanks for the suggestion. We can start with just a simple collator to have pipelines searchable. @stephanschielke As per your question, I think let's use `yarn backstage-cli...

Oh, interesting. Didn't expect it to be a one off glitch.

> and still asking to add relevant annotations. Hi Anuj, can you please share the `catalog-info.yaml` file for the catalog entity you are viewing? I wonder what annotations you have...

@rakeshkumarltim You seem to have added the annotations under the `metadata` field. They should be under `metadata.annotations`. See an example https://github.com/harness/backstage-plugins/blob/main/examples/catalog-harness-cicd-new.yaml

Usually the `harness.io/project-url` starts with the base url e.g. https://app.harness.io - so if the user has not defined the `harness.baseUrl` config in `app-config.yaml`, we should not mandate it, rather extract...

@SarvJ1 Anything you want to add?

Re-opening since plugin suggestion issues are now exempt from [stalebot](https://github.com/backstage/backstage/blob/18f7345a6c29dcfccef7df081b1708f2bf8f62ff/.github/stale.yml#L9).