newrelic / newrelic/release-toolkit
Add more variables to the template mechanisim
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4
- Forks
- 9
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Description
Implementing release-toolkit in a personal open source project I found an issue while link-dependencies.
The change-log that I need to link has a weird URL: https://doc.powerdns.com/authoritative/changelog/4.9.html#change-4.9.1
We would need to add more options to the template function.
It would be awesome to have some templating mechanisim like this:
https://doc.powerdns.com/authoritative/changelog/{{.To | major}}.{{.To | minor}}.html#change-{{.To}}
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
Start in src/changelog/linker/mapper/dictionary.go at the template function referenced by the issue, then trace how link-dependencies applies it. Check the existing template variables and the requested .To transformation. Done means the changelog URL template can express the shown major/minor path and full version anchor without breaking current mappings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100