Skip to content
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

Support nested release labels #4852

Open
iwahbe opened this issue Jul 1, 2024 · 2 comments
Open

Support nested release labels #4852

iwahbe opened this issue Jul 1, 2024 · 2 comments
Labels
kind/enhancement Improvements or new features

Comments

@iwahbe
Copy link
Member

iwahbe commented Jul 1, 2024

Hello!

  • Vote on this issue by adding a 👍 reaction
  • If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

Go allows authors to serve multiple releases out of the same repository via prefixing a release tag with the path to root directory: nested/vX.Y.Z. To allow provider authors to serve multiple packages from the same repo, we should follow the same convention.

Affected area/feature

@iwahbe iwahbe added kind/enhancement Improvements or new features needs-triage Needs attention from the triage team labels Jul 1, 2024
@github-project-automation github-project-automation bot moved this to 🤔 Triage in Docs 📚 Jul 1, 2024
@sean1588 sean1588 moved this from 🤔 Triage to 🧳 Backlog in Docs 📚 Jul 8, 2024
@sean1588 sean1588 removed the needs-triage Needs attention from the triage team label Jul 8, 2024
@cnunciato
Copy link
Contributor

@iwahbe So this is essentially "support monorepos for Registry docs", or is there more to is than that?

@iwahbe
Copy link
Member Author

iwahbe commented Jul 15, 2024

@iwahbe So this is essentially "support monorepos for Registry docs", or is there more to is than that?

No, that's about it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Improvements or new features
Projects
Status: 🧳 Backlog
Development

No branches or pull requests

3 participants