README.md & Marketplace reads: edit the tour's ref by right-clicking it in the CodeTour tree and selecting Change Git Ref. This let's you "rebase" a tour to a tag/commit...
However:
Have a tour with GIT commit reference
Modify the source code above (before) a tour step (tour step having line)
Commit (the source code change) to GIT.
Change the tour's GIT reference to the new commit.
Mainstream understanding/use of term rebase implies that the above steps would update the tour step to have a line number from the new GIT commit. (I'd assume there could be an API to get the line shifts (per file) between two GIT commits for some changes, depending on how GIT generates the deltas.)
Please
implement the above expected behavior (for line-based steps) - especially so if pattern-based steps are likely to be far away, and/or
update README.md and Marketplace to reflect the reality (to save people's confusion and time).
don't close this as a "duplicate" of #141, because then people will stay in the dark.
README.md & Marketplace reads: edit the tour's ref by right-clicking it in the CodeTour tree and selecting Change Git Ref. This let's you "rebase" a tour to a tag/commit...
However:
line)Mainstream understanding/use of term
rebaseimplies that the above steps would update the tour step to have a line number from the new GIT commit. (I'd assume there could be an API to get the line shifts (per file) between two GIT commits for some changes, depending on how GIT generates the deltas.)Please
line-based steps) - especially so if pattern-based steps are likely to be far away, and/orREADME.mdand Marketplace to reflect the reality (to save people's confusion and time).Thank you in advance.