As requested by <a class="user-mention notranslate" data-hovercard-type="user" data-ho

This was closed with <a class="issue-link js-issue-link" data-error-text="Failed to lo

not sure why it didn't auto-close when linked. <p dir="

It was linked in <a class="issue-link js-issue-link" data-error-text="Failed to load t

Yeah. Also, it's not solved because it's not solved. Like on <code class="notransl

Consistently write "bandlimited interpolation" over "band-limited interpolation" about tdms HOT 5 CLOSED

willGraham01 commented on September 7, 2024

Consistently write "bandlimited interpolation" over "band-limited interpolation"

from tdms.

Comments (5)

willGraham01 commented on September 7, 2024

This was closed with #262, not sure why it didn't auto-close when linked.

from tdms.

giordano commented on September 7, 2024

not sure why it didn't auto-close when linked.

Because it wasn't linked?

from tdms.

willGraham01 commented on September 7, 2024

It was linked in #299, which then got merged into #262.

Although saying that, #299 looks like GitHub didn't auto-link this issue from the PR text anyway

from tdms.

giordano commented on September 7, 2024

https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue

Note: The special keywords in a pull request description are interpreted when the pull request targets the repository's default branch. However, if the PR's base is any other branch, then these keywords are ignored, no links are created and merging the PR has no effect on the issues. If you want to link a pull request to an issue using a keyword, the PR must be on the default branch.

Emphasis not mine.

from tdms.