Closed
Conversation
thozza
requested changes
Apr 2, 2026
Member
thozza
left a comment
thozza
left a comment
There was a problem hiding this comment.
The change looks good, but can you please remove the merge commit (the second one)? You can create a PR directly from your fork branch, not your fork main.
Contributor
Author
|
sure @thozza thank you. I was lazy and rushing. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
jira-in-epic stopped working because Jira Cloud has higher GDPR requirements and we can't pass through email addresses as identifiers and have to switch to account IDs.
I retrieved all the account IDs from Jira profiles and replaced them here.
I added @jlsherrill and removed our friend Michael as he will not have a valid Jira ID any more.