kainoa, 1 year ago

@frumble eh, to be fair it was closed "invalid/not as planned" because it was a duplicate of another issue.

frumble, 1 year ago

@kainoa Why would you close this as "not planned", one year after you identified it as a duplicate? (Is this a bot?)

kainoa, 1 year ago

@frumble it's not a bot. GitHub only has two ways of closing issues: Completed or Invalid. Invalid often shows up as "Invalid/Not Planned", or "Not Planned". It's not that they're literally not planning it, they're just not marking it as complete.

kainoa, 1 year ago

@frumble also, i wasn't the one who closed them. I don't work on the Mastodon repo, just an observer.

frumble, 1 year ago

@kainoa I know, was just using is figuratively. Still, why exactly one year after the marking as duplicate?

kainoa, 1 year ago

@frumble wdym? The issue was filed a year ago and closed a year ago.

frumble, 1 year ago

@kainoa No, it was closed 2h ago.

kainoa, 1 year ago

@frumble ah. Probably was just sorting thru stale issues.

pixelcode, 1 year ago

deleted_by_author

frumble, 1 year ago

@pixelcode Dort dürfte dann auch das "closed as not planned" in den nächsten Minuten regnen.

Natanox, 1 year ago

@frumble The moment something like Calckey is supporting full account transfers I'm off to better lands.

kainoa, 1 year ago

@Natanox @frumble we support full account transfers and post imports!

ahriboy, 1 year ago

deleted_by_author

kainoa, 1 year ago

@ahriboy @Natanox @frumble yes.

ahriboy, 1 year ago

deleted_by_author

kainoa, 1 year ago

@ahriboy @Natanox @frumble yep