How do you handle "generic packages" deployment?

This page summarizes the projects mentioned and recommended in the original post on /r/github

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • community

    Public feedback discussions for: GitHub Mobile, GitHub Discussions, GitHub Codespaces, GitHub Sponsors, GitHub Issues and more! (by community)

  • I think it's not about missing commands, but missing destination (package repo of "generic" type). Very same issue posted here: https://github.com/community/community/discussions/38083

  • openapi-gh-pkg

    OpenAPI for GitHub Packages is a tool that generates and publishes libraries based on open API specification files to GitHub packages

  • There are several actions in the marketplace that claim to support "publishing packages". Some of the (this one for example) explicitly support publishing to GitHub Packages. I wonder if you could examine the code and extract the bits that do the publishing in order to publish your files as GitHub Packages. It wouldn't be support for generic packages, but it might solve your current problem.

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts