Overwrite destination duplicates??

[joshbruce]

Possibly even delete all current labels and replace.

-replace

-r

Would be nice to be able to overwrite labels that already exist.

-replace-duplicates

-rd

Don't know if this is possible.

[martin-braun]

The Cli is replacing duplicates at me, so it should be possible by simply using the copy function without any flags. I like the idea to delete all pre-existing labels, though.

[OpticFusion1]

Hey, if you could re-make this issue on my fork that would be nice. This project's dead, and having these issues on my fork will make things easier on me :)

[joshbruce]

Interesting assessment.

What makes you say the project is dead??

(I took over a project once with hundreds of issues, stale PRS, forks, and whatnot - it's pretty revived now and it's own organization account - so curious on the assessment and hopping to a fork over requesting to take over main.)

[OpticFusion1]

last update in general (for the account) was on Mar 1, 2020

[jvandemo]

@joshbruce @OpticFusion1 Thank you for your suggestions and input.

Instead of progressing via a fork, would you be interested to help maintain this repository?

I'd be happy to make you a maintainer for the sake of the progress of this library and its users.

Thanks in advance! 🏆

[OpticFusion1]

@jvandemo I believe the following PRs should fix some of the issues that both CLI and this repo have https://github.com/jvandemo/copy-github-labels-cli/pulls https://github.com/jvandemo/copy-github-labels/pull/14

[joshbruce]

@jvandemo: I'd be interested, but not if I'm the only one - I'm better at the community maintenance thing.

I'm not sure how much development is happening in the forks at this time.

Could we take this library and put it in an org or something - that's what we did with MarkedJS to hand it over to the community (such as it was at the time)?? https://github.com/markedjs

@OpticFusion1: What do you think on that score??

[joshbruce]

ps. As an org. the community could also expand into things like GitHub actions - maybe and other tools. Again, see MarkedJS over the last couple of years.

[joshbruce]

@OpticFusion1: Also, on the commits not being made within 2 years or more - that's not the greatest metric as it doesn't account for different things. The library does one, tiny thing and does it pretty well.

I had an app that Apple took off the App Store because it lacked updates - in that time I never had a bug report from a user nor a feature request from users (and I was a user) - it had, however, been optimized down to just under 2MB for install (from 9MB without losing a single feature). I also have some open source libraries that haven't been updated in years - I use them daily - no issues or feature requests, granted not a lot of users either.

So, I hear you and sometimes we (engineers) can update code that doesn't really need it.

[OpticFusion1]

I'm well aware on how it's not the greatest metic @joshbruce I do program stuff outside of this, check my pinned repos. There's however 9 open issues total, 1 from 2015, 1 from 2017, 3 from 2018, 2 from 2019, and 2 from 2020. This repo was last updated 2 years ago commit wise. The CLI 5. One could consider it dead under those circumstances.

[joshbruce]

Apologies. No judgment or presumption of skill or knowledge meant.

That seemed to be the only evidence presented at trcc ex time.

My basis of comparison was 7y old issues - hundreds and hundreds more PRs. A core team unable to publish, which meant they gave up. At least the repo owner responded on this one - that took months from my basis of comparison.

[OpticFusion1]

Responding does not mean the project is not dead, this PR was closed due to being stale for 1 1/2 years after it was opened.

Then there's my PRs, haven't been touched for 2 days, even though the amount of lines modified is incredibly small https://github.com/jvandemo/copy-github-labels/pull/14 - Modified: 10 lines Removed: 6 lines https://github.com/jvandemo/copy-github-labels-cli/pull/10 Modified: 4 (Bumped dependency versions) https://github.com/jvandemo/copy-github-labels-cli/pull/9 Modified: 2

Dealing with all three would take a few minutes at best yet they've been left for 2 days.

[martin-braun]

Well I'm not planning to work on this repo, but if you would allow me to leave my two cents:

1. @OpticFusion1 You are clearly caring about this repo, so please confirm to @jvandemo you want to maintain this, since he seems to have no time to handle it and he offered you to become a maintainer, thus you don't need any confirmation when you push changes.
2. @jvandemo Maybe consider turning this into a community project as @joshbruce suggested, by creating an organization and moving your repo over. We really value your work and want you to keep credits, but I think it doesn't look good to have a repo with an owner who cannot spend time on it.

[OpticFusion1]

As much as I'd like too, NodeJS isn't my thing, and I have a few other high priority projects that need the most of my time

[joshbruce]

@OpticFusion1: Feel you.

@jvandemo: I could ask the MarkedJS crew. Though to make it easier for them and our CI/CD folks it would probably be best to have the library under that organization. To @martin-braun's point creation credit would remain, just would like the flexibility and signal that it's a community maintained project.