openresty / openresty/headers-more-nginx-module
Use github releases so github API can pull latest version
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.8k
- Forks
- 236
- Avg merge
- 1h 34m
- Merged PRs (30d)
- 2
Description
Right now the repo doesn't technically have any releases, so we can't leverage the github API to find the latest release per https://docs.github.com/en/rest/reference/repos#get-the-latest-release
root@use-mike-lb-internal1:/srv/nginx-1.20.1# curl https://api.github.com/repos/openresty/headers-more-nginx-module/releases
[
]
root@use-mike-lb-internal1:/srv/nginx-1.20.1#
That makes it more of a pain to do programmatically and keep things up to date when building infrastructure as code. Please do this so my life gets easier! :)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by reviewing the repository's existing version and tag history together with its GitHub release configuration; the work is done when a version is published as a GitHub release and the latest-release API returns it for this repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, github
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100