@pbuttigieg I don't see the pull request here yet

No, it's just a branch for now. Don't think we're ready to initiate a PR. we can when we have the other types drafted .

Commit was 62185a1 (in the commit message if you enter "... (issue #11)" it would have tagged it here magically).

Commit was 62185a1 (in the commit message if you enter "... (issue #11)" it would have tagged it here magically).

this issue is linked to the branch where all commits will occur. We don't need to, and shouldn't, cross-reference issues / PRs in each commit message to avoid clutter. exceptions only when there's a need to point to a specific comment in the issue thread .

@pbuttigieg tagging commits to issues (or through a pull request) help discover those commits easily later on (I can understand for yourself, as you made the commit, but months from now that commit would be impossible to find, as no one else would know what branch it lives in).

(explained by PL offline, I apologize for my questions here). I understand now.

never apologise for questions :)

For others - the way that GitHub now allows one to auto-link an issue to a branch (named after the issue) negates the need to tag commits, as the whole branch is linked.

We assume this was implemented to cut down clutter

Here is the latest changes (minor formatting changes): local-contexts-project-example.json

Thanks @jmckenna - getting closer. We have to figure out what properties map to each label and notice, as they are often different kinds of things