Truncate name of timeline records to fit into database field #8372
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
Signed-off-by: Jonathan Mezach <[email protected]>
Signed-off-by: Jonathan Mezach <[email protected]>
dosubot
bot
added
size:XS
|
Thanks for the PR. |
Signed-off-by: Jonathan Mezach <[email protected]>
dosubot
bot
added
size:S
|
@klesh Ah, yes of course. Sorry about that, pretty new at Go as a programming language. I believe I've fixed it now though ;) |
klesh
approved these changes
Apr 8, 2025
|
Thanks for your contribution. |
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.
pr-type/bug-fix,pr-type/feature-development, etc.Summary
This simply truncates the name of an Azure DevOps timeline record so that it fits into the underlying database table. Since these names aren't used anywhere else we believe it is fine to just truncate it.
Does this close any open issues?
Closes #8325
Screenshots
N/A
Other Information
See discussion in #8325 for details.