- The repository has a master branch for code contributions / pull-request.
- The issues section is also used by “normal” users (e.g. for questions / or to see yet unresolved bugs (e.g. partially with workarounds)).
- Closing an issue for the master branch (e.g. from a commit), also closes the issue in the issues section, even though there’s no release with that commit yet, so people will get confused sooner or later, since it’s marked as closed.
How would or already do you go about organizing this / or solving this in another way?
Things we already tried:
In the past we had a special upcoming branch, where I pushed changes to, so after a new version was released, I would only then merge it to master, thus auto-closing the issues.
The problem with that is, that coders usually want to make pull-requests onto the master branch.
Suggestion (Maybe not doable with reasonable effort?):
Ideally I wouldn’t want issues auto-closed until the commit is merged into latest release (not pre-release).