tryfabric / memorable-milestones Goto Github PK

Something like 🍎 Apple (May 14), so it's easier to know when the sprint is ending.

Create milestones with a slight delay in between. By default, the milestones page is sorted by recently updated, so we'd actually want to create them backwards alphabetically.

Currently, milestones closed manually do not get the "(closed $date)" appended to them. That means they will conflict when the name gets reused in a future cycle.

We use this action in a repository that does not have a lot of issues, so some of the generated milestones do not have any issues, and thus are never closed.

Why not closing all outdated milestones with no opened issues or prs, regardless of the total number of issues they have?
Or at least exposing the parameter in the config (breaking zero-config in this case)?

For now, we have to manually close the milestones, which is not so great 😉

Should make the function that detects if a milestone already exists more flexible, so users can append things to the title or close it, without it getting recreated.

Also note in the docs that if you want to skip a week, just close it!

To tweet the milestones as they start and end.

If a milestone is past its due date and all issues are closes (regardless of the # of issues closed), close it.

Right now, we only close it if it has a minimum of 3 issues in it. We'd want to remove this minimum.

If the milestone is closed, shouldn't create a new one.

Should just look at all milestones, not only open ones.

Hello, we created this issue becuase the user @marissamarym told us you are calling for maintainers.
✅ If you're looking for collaborators no action is required.
👮🏻‍♂️ If this repo is well-supported please put a comment here sospedra/rfm#70 and we'll close it immediately.
Sorry for any inconvinience. We understand this message can feel spammy but we really think is good to double-check first with the current owners :)

Hello, just to understand, is there any way we can easily configure it to program due dates for days different than Thursdays?

Since the milestones are cyclical, we recreate milestones with the same name, so adding the date to closed milestones will make titles unique, for both closed and open milestones.

Basically, there should never be two milestones with the same title, regardless of if they're open or closed.

After completing this bug, we'll also want to make a new release.

Tag closed milestones with (closed) because GitHub doesn't let you create milestones with same title

So it's easy to move everything that isn't in a sprint into there.

Release a new version.

got duplicate sprint starting messages for two different milestones. We are starting map milestone but got notified for both the Map and Orange milestones this week