You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello @motemen, @onk, and the git-pr-release maintainers,
Currently, git-pr-release lacks the ability to create Draft PRs. This imposes the assumption that all PRs are fully prepared, which may not always reflect the actual situation.
Proposed Solution
I propose to add a setting named pr-release.draft, which should be specified as a boolean value. By default, it will be set to false. However, when users set it to true, the PRs created by git-pr-release will be marked as drafts.
Additional Information
Adding this functionality to git-pr-release would allow users to communicate more clearly to other developers that their work is still ongoing. I believe this could greatly improve the workflow and collaboration within development teams.
The text was updated successfully, but these errors were encountered:
Hello @motemen, @onk, and the git-pr-release maintainers,
Currently, git-pr-release lacks the ability to create Draft PRs. This imposes the assumption that all PRs are fully prepared, which may not always reflect the actual situation.
Proposed Solution
I propose to add a setting named
pr-release.draft
, which should be specified as a boolean value. By default, it will be set tofalse
. However, when users set it totrue
, the PRs created by git-pr-release will be marked as drafts.Additional Information
Adding this functionality to git-pr-release would allow users to communicate more clearly to other developers that their work is still ongoing. I believe this could greatly improve the workflow and collaboration within development teams.
The text was updated successfully, but these errors were encountered: