scala / scala/make-release-notes
Resolve release date from tag on GitHub
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 82
- Forks
- 79
- PR merge metrics
- No merged PRs in 30d
Description
If you leave out the release date parameter for MakeDownloadPage it'll just take current date. That's probably not what you want because we should use date of when the tag was created.
It's possible to resolve it using GitHub's API:
curl -s https://api.github.com/repos/scala/scala/git/refs/tags/v2.11.0-M5 | json object.url | xargs curl -s | json tagger.date
2013-09-07T00:05:56Z
assuming the jsontool is installed.
//cc @retronym
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
Locate the MakeDownloadPage entry point and trace how its release date is selected. Read the GitHub tag reference and tag metadata endpoints shown in the issue, then verify that an omitted date uses the tagger date while an explicit date still works. Confirm the generated release notes use the resolved date.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, scala
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100