Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Update GitHub PR template #60872

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
wants to merge 2 commits into
base: 6.4
Choose a base branch
from

Conversation

javiereguiluz
Copy link
Member

Q A
Branch? 6.4
Bug fix? no
New feature? no
Deprecations? no
Issues -
License MIT

Proposed changes:

  • Make some instructions more concise and actionable
  • Emphasize that PRs without a proper description are discouraged
  • Add a few emojis; not for decoration, but to improve visual separation and readability

@javiereguiluz javiereguiluz added this to the 6.4 milestone Jun 23, 2025
@carsonbot carsonbot modified the milestones: 6.4, 7.4 Jun 23, 2025
@carsonbot

This comment was marked as resolved.

@javiereguiluz javiereguiluz changed the base branch from 7.4 to 6.4 June 23, 2025 06:51
@javiereguiluz javiereguiluz modified the milestones: 7.4, 6.4 Jun 23, 2025
Comment on lines +20 to +21
- ✨ New features and deprecations must target the **in development** branch
- 📝 Add a changelog entry:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- ✨ New features and deprecations must target the **in development** branch
- 📝 Add a changelog entry:
- ✨ New features and deprecations must target the **feature** branch
and must add an entry to the changelog file of the patched component:

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"feature branch" is something that we never mention in Symfony site or docs, so this could be confusing to folks.

We only mention:

  • Stable
  • LTS
  • Maintained
  • Unmaintained
  • Under development
  • Security fixes only

Source: https://symfony.com/releases

Copy link
Member

@nicolas-grekas nicolas-grekas Jun 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"feature" is the word we use on line 1 of the table, so that might be easier to understand than "in dev", which is not explained in the template

Copy link
Member

@nicolas-grekas nicolas-grekas Jun 24, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't miss that my suggestion is also about merging the changelog entry suggestion with the feat/deprec line. As is now, people might be confused and think they should add one for bugs too I fear.

@mttsch
Copy link
Contributor

mttsch commented Jun 24, 2025

As I have been removing some deprecated code for 8.0, I was also always wondering how to fill out the table: It is no bug fix, it is no (new) feature, and it is also no deprecation, because it resolves the deprecation. Not sure if you would really somehow include this case to help filling out the table. (Setting everything to "no" also looks "weird" …)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants