Repository navigation
Conversation
(cherry picked from commit 96c78a3)
Author
|
@milanmajchrak customer/lindat specific - not wanted on dtq-dev? |
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
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.
References
customer/lindat(pushed directly, no PR)Description
scripts/sourceversion.pysetsRELEASE_TAG_BASE='lindat'instead of'none'. The value builds the "Release link" in the generated version page.Instructions for Reviewers
List of changes in this PR:
-x, no conflicts. The patch is identical to the source commit.Problems
.../releases/tag/lindat-<yyyy.mm.>...links.How to test:
python scripts/sourceversion.py <run-url-prefix> <run-id>; the release link starts withlindat-.AI Disclosure
Claude Code made the cherry-pick and wrote this description. The net diff was checked against
customer/lindat.