Skip to content

🚀 Feature: Bring in a require-repository rule #867

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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
3 tasks done
JoshuaKGoldberg opened this issue Feb 3, 2025 · 2 comments
Open
3 tasks done

🚀 Feature: Bring in a require-repository rule #867

JoshuaKGoldberg opened this issue Feb 3, 2025 · 2 comments
Labels
status: accepting prs Please, send a pull request to resolve this! 🙏 type: feature New enhancement or request 🚀

Comments

@JoshuaKGoldberg
Copy link
Owner

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.

Overview

Following #42 -> #51: we've resolved to create a standalone require-repository rule. It should enforce that the field exists in the package.json file.

Additional Info

💖

@christopher-buss
Copy link

This would be useful, as it's a requirement to have the repository field when deploying with npm config provenance.

@michaelfaith
Copy link
Collaborator

This would be useful, as it's a requirement to have the repository field when deploying with npm config provenance.

If you have an opinion on whether or not this should be included in the recommended config, feel free to add your thoughts here: #850

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: accepting prs Please, send a pull request to resolve this! 🙏 type: feature New enhancement or request 🚀
Projects
None yet
Development

No branches or pull requests

3 participants