Git log using tempo id instead of jira id #69
Closed
Conversation
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
joegrimer
commented
Apr 1, 2025
| @@ -53,7 +53,7 @@ export default { | |||
| } | |||
| const issueKey = await aliases.getIssueKey(input.issueKeyOrAlias) ?? input.issueKeyOrAlias | |||
There was a problem hiding this comment.
I plan to add a bit here that translates the jira key. I think I need to create a new axios
|
Thanks for the contribution, I migrated the tool to the new API here: #70 so I am closing this PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
From: #66
I used these instructions and https://apidocs.tempo.io/#tag/Worklogs/operation/getWorklogById
to try and cobble together something locally. Naturally I had to switch to v4, which breaks all the other commands (though given how few things needed to change, I suspect that can be fixed too). I got tempo log to work, and was wondering whether I ought to integrate @wojciech-kulik 's suggestion somehow (but that would require another api object, I believe)
I've never written node before, nor contributed to a repo like this before, so am not sure how to proceed. So far, it's a hacky 4 line change