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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃殌 Feature: Use a shenanigans.json file instead of a "shenanigans" package.json property #300

Open
3 tasks done
JoshuaKGoldberg opened this issue Aug 19, 2022 · 0 comments
Labels
area: tooling Builds, infrastructure, packages, and other repository management package: shenanigans-manager type: feature Suggested enhancement or new ability.

Comments

@JoshuaKGoldberg
Copy link
Member

Bug Report Checklist

  • I have tried restarting my IDE and the issue persists.
  • I have pulled the latest main branch of the repository.
  • I have searched for related issues and found none that matched my issue.

Expected

I'm finding now that there are a lot of reasons to include metadata around a package's shenanigans-manager process (e.g. #298, #299). I think it's time to make a dedicated shenanigans.json file instead of a big property in package.json files.

Additional Info

Fun fact, this was used five+ years ago, but removed in #22. At the time shenanigans.json files just included package metadata already present in package.json.

@JoshuaKGoldberg JoshuaKGoldberg added type: feature Suggested enhancement or new ability. package: shenanigans-manager area: tooling Builds, infrastructure, packages, and other repository management labels Aug 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: tooling Builds, infrastructure, packages, and other repository management package: shenanigans-manager type: feature Suggested enhancement or new ability.
Projects
None yet
Development

No branches or pull requests

1 participant