Skip to content

Correct way to reference issue (non-closing) in commit message #2735

@ishazel

Description

@ishazel

I have an open feature request. I implemented a basic version of the feature but didn't want to close the issue, so instead of adding Resolves: #101 to the commit message, I added Refs: #101.

GitHub knew that I was referencing, not closing, the issue, but Release Please noted in it's PR body and in the changelog that the commit closed the issue.

Is this behavior expected? Is there a more appropriate way to do this?

Metadata

Metadata

Assignees

Labels

priority: p3Desirable enhancement or fix. May not be included in next release.type: questionRequest for information or clarification. Not an issue.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions