chore: Delete the pull request template #11301
Open
+0
−12
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
didinele
approved these changes
Nov 25, 2025
almostSouji
approved these changes
Nov 25, 2025
almeidx
approved these changes
Nov 25, 2025
vladfrangu
approved these changes
Nov 25, 2025
Member
vladfrangu
left a comment
vladfrangu
left a comment
There was a problem hiding this comment.
I feel like we could've kept at least the first header but I know even we struggle to write proper content in there 😄
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Before the monorepo, discord.js was only the discord.js package. The pull request template made sense (test your API changes, shout if your changes are breaking, and more).
Now, it contains packages like @discordjs/brokers, @discordjs/actions, the api-extractor packages, as well as the website and guide applications. Semantic versioning doesn't really apply to these, and testing API changes certainly doesn't apply for the websites.
I'm moving towards removing the file. At the very least, the status and versioning classification should be removed as we double-check that anyway (it duplicates work). This results in only describing changes, which is common sense.
Open to ideas to generalise this, but I don't think that's possible unlike issue forms.