Skip to content
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.

Document usage & publishing steps for buildpack registry #167

Closed
edmorley opened this issue May 5, 2020 · 1 comment
Closed

Document usage & publishing steps for buildpack registry #167

edmorley opened this issue May 5, 2020 · 1 comment

Comments

@edmorley
Copy link
Member

edmorley commented May 5, 2020

This buildpack is published to the buildpack registry:

$ h buildpacks:versions heroku-community/static
Version  Released At               Status
───────  ────────────────────────  ─────────
1        2019-09-18T17:53:50.634Z  published
         2019-09-18T17:53:50.637Z  pending

It would be good to:

  1. Have the README list the heroku-community/static alias as the recommended way to add the buildpack (not the git URL)
  2. Add publishing steps to remind people making changes to publish them to the registry
@edmorley
Copy link
Member Author

(1) was fixed by #194.

(2) still needs resolving.

@edmorley edmorley closed this as completed Jun 9, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant