pull_request_template.md

Rama main · réplica de lectura del repositorio original.

<!--
# Instructions

1. Pick a meaningful and result-oriented title for your pull request. Describe the result and keep the full title under 70 characters.
  - Use the format `<emoji> <type>: <description>` with a lowercase conventional prefix and description, for example: `✨ feat: isolate malformed flag and segment evaluation errors`.
  - Choose a conventional prefix that matches the change, such as `feat`, `fix`, `style`, `refactor`, `docs`, `test`, `perf`, `build`, `ci`, `chore`, or `revert`. An optional scope is allowed: `<emoji> <type>(<scope>): <description>`.
  - Prefix the title with an emoji to categorize what is being done. (Copy-paste the emoji from the list below.)
  - Assign the appropriate label(s) to the pull request. (Use one of the labels from the list below.)
  
2. Enter a succinct description that says why the PR is necessary, and what it does.
  - Implement aspect X
  - Leave out feature Y because of A
  - Improve performance by B
  - Improve accessibility by C

3. Provide clear testing instructions that include any pertinent information, i.e. seat, roles, etc.
4. Include screenshots of your changes if they impact the UI (Before & After).
5. Update the preview link with your pull request number.
6. Include any JIRA tickets, design documents, GitHub issues, or other related items to the bottom of the PR.

# Available labels
UI
API
Evaluation Server
OLAP

# Emojis for categorizing pull requests

✨ New feature or functionality
🐛 Bugfix
🔥 P0 fix
✅ Tests
🚀 Performance improvements
🖍 CSS / Styling
📖 Documentation
🏗 Infrastructure / Tooling / Builds / CI
↩️ Reverting a previous change
🧹 Refactoring / Housekeeping
🔧 Package Upgrades / Maintenance
🗑️ Deleting code

-->