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

Milestone Reminder GH Action doesn't always work #42835

Open
nemanjaglumac opened this issue May 17, 2024 · 3 comments
Open

Milestone Reminder GH Action doesn't always work #42835

nemanjaglumac opened this issue May 17, 2024 · 3 comments
Assignees
Labels
.CI & Tests .DX Developer experience and QoL related.

Comments

@nemanjaglumac
Copy link
Member

Describe the bug

We have a very useful milestone reminder GH action, but it doesn't always work as expected.
There are two scenarios we need to fix:

  1. The action sometimes literally fails because of an exception (example)
  2. The action posting a comment on PRs that don't even have the closing keyword (example)

To Reproduce

  1. Close a PR that contains this body: Closes #12345 and #23456

or

  1. Close a PR that doesn't have a closing keyword at all.

Expected behavior

  1. Action should never fail
  2. Action should not post comments on PRs that didn't have the closing keyword and a linked issue to begin with

Logs

No response

Information about your Metabase installation

.

Severity

p3

Additional context

Internal.

@nemanjaglumac nemanjaglumac added Type:Bug Product defects Priority:P3 Cosmetic bugs, minor bugs with a clear workaround .CI & Tests .DX Developer experience and QoL related. labels May 17, 2024
@nemanjaglumac nemanjaglumac self-assigned this May 17, 2024
@darksciencebase
Copy link
Contributor

I'm probably missing something, but if a PR doesn't have a closing keyword, that means it's not connected to an issue, which in turn means the PR itself should have a milestone, so I'm lost about the #2 in the description.

@nemanjaglumac
Copy link
Member Author

which in turn means the PR itself should have a milestone

Not always. There are a ton of tech debt PRs that don't really need a milestone. I'm not aware that we're enforcing a milestone in 100% of cases?

@darksciencebase
Copy link
Contributor

Not always. There are a ton of tech debt PRs that don't really need a milestone. I'm not aware that we're enforcing a milestone in 100% of cases?

not 100% but (1) better too many PRs than too few, (2) many tech debt PRs should have a milestons, (3) the reminder doesn't know a difference. let's continue this discussion on the notion doc explaining our usage of milestones

@ranquild ranquild removed Type:Bug Product defects Priority:P3 Cosmetic bugs, minor bugs with a clear workaround labels May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
.CI & Tests .DX Developer experience and QoL related.
Projects
None yet
Development

No branches or pull requests

3 participants