2-feature_request.yml 1.5 KB

12345678910111213141516171819202122232425262728293031323334353637
  1. name: Feature request 🚀
  2. description: I have a suggestion about a new feature (and may want to implement it)!
  3. labels: [ "kind/feature request", "status/to verify" ]
  4. body:
  5. - type: markdown
  6. attributes:
  7. value: |
  8. Before requesting a new feature, make sure your version of PHP-CS-Fixer is up-to-date.
  9. > [!IMPORTANT]
  10. > For initial ideas it's preferable to use [discussions](https://github.com/PHP-CS-Fixer/PHP-CS-Fixer/discussions/categories/feature-ideas).
  11. As a maintainers we prefer to have only actionable issues in the backlog, with clear definition of done,
  12. that's why Discussions are the best way to start. When scope of the request is established, then actual issue can be created.
  13. - type: textarea
  14. id: feature-request
  15. attributes:
  16. label: Feature request
  17. description: Please describe the feature you would like to see implemented.
  18. validations:
  19. required: true
  20. - type: input
  21. id: discussion-reference
  22. attributes:
  23. label: Link to Discussion where feature request was formed
  24. placeholder: "https://github.com/PHP-CS-Fixer/PHP-CS-Fixer/discussions/<ID>"
  25. validations:
  26. required: false
  27. - type: checkboxes
  28. id: terms
  29. attributes:
  30. label: Contribution Checks
  31. options:
  32. - label: I have verified if this feature request was already discussed
  33. required: false
  34. - label: I am familiar with ["Feature or bug?"](https://github.com/PHP-CS-Fixer/PHP-CS-Fixer/blob/master/feature-or-bug.rst)
  35. required: false