Skip to content
This repository has been archived by the owner on Jan 10, 2024. It is now read-only.

updated buildpack URL after merge with PR #40 #41

Merged
merged 1 commit into from Oct 26, 2022

Conversation

abernicchia-heroku
Copy link
Contributor

Now it's also necessary to publish the buildpack so the Heroku Elements page (basically README.md) for the buildpack (https://elements.heroku.com/buildpacks/postgrest/postgrest-heroku) is aligned with GitHub too - see https://devcenter.heroku.com/articles/buildpack-registry#publishing-a-buildpack-version

Now it's also necessary to publish the buildpack so the Heroku Elements page (basically README.md) for the buildpack (https://elements.heroku.com/buildpacks/postgrest/postgrest-heroku) is aligned with GitHub too - see https://devcenter.heroku.com/articles/buildpack-registry#publishing-a-buildpack-version
@steve-chavez steve-chavez merged commit 4e4eef1 into PostgREST:main Oct 26, 2022
@steve-chavez
Copy link
Member

It's been a while since I've used Heroku.

@abernicchia-heroku I was wondering, would you like to help us in maintaining this repo?

What would you need to publish the buildpack?

@abernicchia-heroku
Copy link
Contributor Author

@steve-chavez yes, sure I can help! However, it is needed to find the original creator who registered the Heroku buildpack for the first time. As per the documentation https://devcenter.heroku.com/articles/buildpack-registry#namespaces-and-buildpack-ownership a buildpack can be owned by an individual (e.g. Heroku personal account) or a Heroku Team. If the latter option has been used you can add me to that Team so I can manage it, otherwise, I would need the user credentials to access.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants