You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the semconv repo, we want to generate links to the issue/PR numbers in the changelog to make it easier to navigate. Because the field issues today can hold both, I think it is not possible to generate the changelog the way we want. For example:
{{- define "entry" -}}
- `{{ .Component }}`: {{ .Note }} (
{{- range $i, $issue := .Issues }}
{{- if $i }}, {{ end -}}
[#{{ $issue }}](https://github.com/open-telemetry/semantic-conventions/issues/{{ $issue }})
{{- end -}}
)
So, it would be great if we could have another field pull_request in the template, so we could use it instead of the issue for semconv (as there it's almost always more interesting to see the actual changes in the changelog).
Today, the template has a field for specifying an issue https://github.com/open-telemetry/opentelemetry-go-build-tools/blob/main/chloggen/internal/chlog/entry.go#L41. In many repos using chloggen, the same field is also used for PR numbers (when there's no issue for example).
In the semconv repo, we want to generate links to the issue/PR numbers in the changelog to make it easier to navigate. Because the field
issues
today can hold both, I think it is not possible to generate the changelog the way we want. For example:So, it would be great if we could have another field
pull_request
in the template, so we could use it instead of the issue for semconv (as there it's almost always more interesting to see the actual changes in the changelog).For context: open-telemetry/semantic-conventions#1627
The text was updated successfully, but these errors were encountered: