Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cross-reference to issues within different projects #751

Open
syphernl opened this issue Dec 16, 2024 · 0 comments
Open

Cross-reference to issues within different projects #751

syphernl opened this issue Dec 16, 2024 · 0 comments

Comments

@syphernl
Copy link

syphernl commented Dec 16, 2024

Our setup consists of:

  • 1 repo: management-repo containing all issues
  • various repo's with the actual code (e.g. code-1, code-2, code-99)

If changes are made people refer to the issue in the management repo like this: fix: something (management-repo#1234) or fix: management-repo#1234 something fixed.
However, the release generator links all of these issues against the code repository instead of the management repo.

Within GitLab, if the MR has a reference to an external repo it gets linked properly (e.g. in the MR title).
I tried to set the issuePrefixes to ["management-repo#"] but this still links the found issue to the code-repo rather than the issue-repo.

Is there a way to tell the release-notes-generator to use a different base URL for the issues? It appears that the only way of doing that would be overwriting the commit.hbs and hardcoding the part of the owner + repository or is there an easier way of achieving this?


edit:

It seems that issueUrlFormat: "{{host}}/{{owner}}/management-repo/-/issues/{{id}}", does the trick, however this only makes the second portion clickable instead of the entire line. I was hoping setting issuePrefixes: ["management-repo#"] in parserOpts but this somehow adds in , closes management-repo#1234 rather than making the occurrences clickable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant