Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support pull requests without associated issues #79

Open
motiz88 opened this issue Sep 14, 2017 · 1 comment
Open

Support pull requests without associated issues #79

motiz88 opened this issue Sep 14, 2017 · 1 comment

Comments

@motiz88
Copy link

motiz88 commented Sep 14, 2017

Pull requests have all the discussion, tagging, search, project management, and other features of issues. But often, in a gren-enabled project, I'm still forced to create a separate issue when I've already made the PR that would close it (e.g. for a previously-unreported problem) because otherwise, the release notes would be incomplete. This adds overhead to what can be a seamless GitHub workflow.

The solution: I think gren should treat merged PRs as their own, self-closing issues if they don't explicitly close any other issue.

@alexcanessa alexcanessa added this to the 0.9.0 milestone Sep 19, 2017
@alexcanessa alexcanessa modified the milestones: 0.10.0, Next Version Oct 8, 2017
@alexcanessa alexcanessa modified the milestones: Release 0.14.0, Next Version Dec 8, 2017
@alexcanessa
Copy link
Member

I've chatted with GitHub APIs team and there is no way in the APIs to detect whether a PR closes any issues.

They're actually suggesting a RegExp against the keywords.

Still, something to address.

@alexcanessa alexcanessa removed this from the Next Version milestone Sep 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants