~ knotless Search/
↑↓ move↵ open⇧↵ all results

chadtmiller.com/knotless

git that lives in your Atmosphere account

knotless.dev
1 collaborator

knotless 0.13.0 Latest 2 packages, 1 image

1
10

An issue's page shows nothing of the pulls that mention it until one closes it

Closed
Closed chadtmiller.com opened this issue 0 comments
kind/featurearea/webarea/serve

What happened

A pull that names an issue, in its body or title, shows on that issue's page only if it merges into the default branch with a closing keyword (Fixes <issue>), as the pull that closed it (closedBy in getThread). Until then, or when it names the issue without a closing keyword ("see", "for"), nothing on the issue says the pull exists. The pull's page lists the issues it names, but the link runs one way.

So an issue's author, or anyone reading the issue, cannot see that work on it is under way. To link work to an issue without closing it, say a docs pull that answers part of a discussion, one has to comment on the issue by hand.

GitHub shows each mention as it is made: an entry on the issue's timeline, "mentioned this pull request", with the pull's state, and a pull with a closing keyword under the issue's "Development" while open.

How to see it

  1. Open a pull whose body names Tangled compatibility? without a closing keyword, as The workflows guide shows how to mirror a repository to another git host does.
  2. Open the issue's page on knotless.dev: the pull is nowhere on it.

What you expected

The issue's page lists the pulls that mention it, each with its state, from the time each is opened, set apart from those that will close it on merge. Perhaps the issue's author hears of it too.

Where

knotless.dev pages, and knotless show on an issue.