Unfork this repository

[voxpelli]

As with eslint-community/eslint-plugin-n#55 we should unfork this repository instead of waiting even longer for the maintainer to possibly hand over the original repository

[github-actions]

This issue has been automatically closed because we haven't received a response from the original author 🙈. This automation helps keep the issue tracker clean from issues that aren't actionable. Please reach out if you have more information for us! 🙂

[github-actions]

This issue has been automatically closed because we haven't received a response from the original author 🙈. This automation helps keep the issue tracker clean from issues that aren't actionable. Please reach out if you have more information for us! 🙂

[voxpelli]

@MichaelDeBoey That bot is far too aggressive. It should at least comment when it adds the label.

Also: Do we actually need it right now? I would prefer us to skip it and leave issues open until we can see that it’s a real problem.

[github-actions]

This issue has been automatically closed because we haven't received a response from the original author 🙈. This automation helps keep the issue tracker clean from issues that aren't actionable. Please reach out if you have more information for us! 🙂

[MichaelDeBoey]

@voxpelli I don't see any harm in keeping the fork status tbh as it's clearly a fork of the original one 🤷‍♂️
Are there any specific things we currently can't do because it's still a fork?

Keeping the fork also keeps the extra link on the original repo + people coming by this repo can see that it's a maintained fork instead of a new repo with about the same name

[github-actions]

This issue has been automatically closed because we haven't received a response from the original author 🙈. This automation helps keep the issue tracker clean from issues that aren't actionable. Please reach out if you have more information for us! 🙂

[voxpelli]

One clear drawback with keeping this as a fork is that GitHub is set up so that it assumes that forks will upstream their changes.

Hence when creating a PR through a link like https://github.com/eslint-community/regexpp/pull/new/voxpelli/remove-stalebot it will not open a PR towards this repository, it will suggest opening a PR to https://github.com/mysticatea/regexpp, which is both error prone and confusing.

And when doing gh repo clone eslint-community/regexpp GitHub also sets up mysticatea/regexpp as an upstream remote, which is needless as that upstream is not an actual upstream, its an historical artifact at this moment in time.