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

GitHub action to validate is any user is assigned to pull request #1092

Closed
adamfilipow92 opened this issue Sep 4, 2020 · 2 comments · Fixed by #1310
Closed

GitHub action to validate is any user is assigned to pull request #1092

adamfilipow92 opened this issue Sep 4, 2020 · 2 comments · Fixed by #1310

Comments

@adamfilipow92
Copy link
Contributor

Author the user story for this feature

As a pull request author, I want to be informed when I forgot to assign my self to pull request so I can avoid empty author on release notes.

Is your feature request related to a problem? Please describe.

I forgot to assign myself to this pr: https://github.com/Flank/flank/pull/1087this cause no author assigned in release notes,


- [#1087](https://github.com/Flank/flank/pull/1087) Fix release action ()

#1089

Describe the solution you'd like
Action should fail when no one is assigned to pull requests.

Describe alternatives you've considered

The alternative is assign the author of the first commit in pull request.

@Sloox
Copy link
Contributor

Sloox commented Sep 4, 2020

@adamfilipow92 I saw this github action. It might not check exactly but it can be triggered first and will do all the work automatically.
https://github.com/marketplace/actions/auto-assign-action

@bootstraponline
Copy link
Contributor

Maybe we should create a github action that copies the label, estimation, and asignees from the issue referenced in the pull request to the pull request itself. This would involve using the ZenHub API.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants