You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repository is about to be locked and archived. Take immediate action to prevent that from happening.
This issue was automatically generated by the Durable Ownership Bot. This repository will be locked in 30 days (2025-05-24) if the ownership information is not updated. To prevent the repository from being locked, please update the ownership by setting the custom properties:
ownership-type: Use either Service Catalog or Hubber Handle.
ownership-name: Provide the corresponding ownership value by specifying @<hubber_handle> if the service is owned by a Hubber, or the name of the service from the Service Catalog if it is owned by a catalog entry. Do not use the long_name or description of the service entry; instead, ensure you use the name of the catalog entry. The name can be found in the ownership.yaml file of the catalog entry or derived from the service URL. For example, in the case of the Service Catalog, the name is cat, as indicated by the URL https://catalog.githubapp.com/services/cat/slos.
Go to the custom properties settings page and populate the ownership-type and ownership-name custom properties. Make sure they are valid since the bot will validate them.
Step 3
Close this issue only once the custom properties have valid ownership information. If the ownership is not updated/valid, the bot will re-open this issue.
Important
This repository is about to be locked and archived. Take immediate action to prevent that from happening.
This issue was automatically generated by the Durable Ownership Bot. This repository will be locked in 30 days (2025-05-24) if the ownership information is not updated. To prevent the repository from being locked, please update the ownership by setting the custom properties:
ownership-type: Use eitherService CatalogorHubber Handle.ownership-name: Provide the corresponding ownership value by specifying@<hubber_handle>if the service is owned by a Hubber, or the name of the service from the Service Catalog if it is owned by a catalog entry. Do not use thelong_nameordescriptionof the service entry; instead, ensure you use thenameof the catalog entry. The name can be found in theownership.yamlfile of the catalog entry or derived from the service URL. For example, in the case of the Service Catalog, the name iscat, as indicated by the URL https://catalog.githubapp.com/services/cat/slos.Step 1
Review the repository ownership documentation.
Step 2
Go to the custom properties settings page and populate the
ownership-typeandownership-namecustom properties. Make sure they are valid since the bot will validate them.Step 3
Close this issue only once the custom properties have valid ownership information. If the ownership is not updated/valid, the bot will re-open this issue.
Please reach out to #repos-durable-ownership if you have any questions, feedback, or concerns.