Then do it because that's the "style" we've been using, just like we use the changes.xml "issue" attribute to refer to the associated Jira issue, but in this case it's not a Jira #, it's a PR#.
Note that the Maven changes plugin does not know about PRs in that field, so we use the PR# in the description. Maybe that plugin can be configured to work with both Jira and GitHub links but that's a different topic. Gary
