Migration of feature requests to tasks/issues for development

[sytone]

What does this look like? GitHub has good integration with issues and branches and PRs. For any feature is there a 'promotion' to an issue template that captures the scenario for the feature?

[claremacrae]

Interesting. It's nice that GitHub adds links between issues and PRs, when a comment in one mentions another, they auto-cross-link...

But I learned recently that Discussions don't get links to any issues or PRs that mention them, which hurts discoverability somewhat...

[sytone]

yes, also if you are using tools like VSCode you can use the GitHub extension and right click to start working on a issue and it makes the branch for you and switches. Also makes the publishing of the PR simpler.

[claremacrae]

Wow, that’s really nice.

[sytone]

yeah, it also allows you to see the PR in VSCode so you can add comments as you work beside the code. You can make issues from VSCode as well.

https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github

[sytone]

@schemar how do you want to track new features being added to the system? I am seeing discussions which are issues/feature requests and there are issues that are both as well.

I just want to follow what you think is the best for your project. Is this the plan?

Issues: Things not happening as expected by the user. These then get associated with a PR to fix a feature that exists but has a problem.

Discussion: Requests and discussions around a new feature for the plugin, this is there the 'spec' is proposed and then this gets associated with the PR.

If an issue or discussion is tracking the other, it can be pushed to the opposite type. For branch naming in the for it could be something like /issue123-friendly-name or /discussion124-friedlyname.

Thoughts?