Simplify Setup

[nateaxcell]

This is an automated PR from the Simplify team,

Apologies for the duplicate branches, we've had issues with GitHub's secondary rate limit! Please disregard our previous branches (e.g. move-from-colophon-to-simplify-retry) or duplicate PRs from us.

more information available here.

Colophon is being deprecated!

Context: Over the last 6 months the Simplify team has been experimenting with a fresh version of Backstage that's centred around Software Catalog. This means that we will no longer need colophon files (however we recommend keeping it until we announce all their dependencies are removed).

What does this Pull Request do?

This PR copies the existing contents of your colophon file and creates a new catalog-info.yaml file, which is then picked up by Simplify and places this repository in the software catalog. No other changes are made to your repository, and your colophon file is left intact.

In the future, we will announce the finalized deprecation of Colophon. At that time, expect another automated PR from us removing your colophon file once it is safe to do so.

Why do you want to do this?

Our goal is to make things easier to find, make actions on your repos take less time to do, and provide insights into the things that you need to know in order to do your jobs effectively.

Software Catalog is the basis for Backstage (Simplify). By adding your catalog-info into your repo (in the pull request that likely took you here) you will be registered automatically in the catalog. This unlocks a lot of features in Backstage that you will be able to take advantage of, including:

• Dynatrace
• JIRA
• PagerDuty
• GitHub Actions
• Team Hierarchy
• Software Templates
• Kubernetes
• (with many more on our roadmap coming!)

What do we need from you?

All you need to do is merge this PR and your repo will be picked up automatically!
If you want to take advantage of some of the other features of Backstage, you will require some additional config in your yaml file (but this is a one time thing!). Here are more instructions on how to do that.

We also recommend setting up a GitHub CODEOWNERS file (instructions here). This is used to to set ownership of your repo in our portal.

If you have more questions reach out in #simplify-hub and we'll be happy to help you out.

Happy coding!

-- The Simplify Team 🚀

[github-actions]

Packages pending updates:

- @tds/community-date-picker: 1.1.0 => 1.1.1

If this is not what you expected, ensure that your commit messages follow the TDS commit types guide on this page: https://tds.telus.com/contributing/developer-guide.html and try again.