# 🚀 Merge Pull Request Template

## 📅 Release Timeline
- **Are we during the dry-run period?**
  - [ ] Cycle A
  - [ ] Cycle B
  - [ ] None of them
  - **If yes, are we merging code to a component that is planned to be released in this release?** 
    - [ ] Yes
    - [ ] No
    - [ ] N/A
   
> [!CAUTION]
> If you answered yes to both questions, consult with TL/GM about risks.
 
---

## 🧪 Testing
- **In which environment did you test it?** 
  - [ ] Locally
  - [ ] Starwars environment
- **How did you test it?** Manually or with component tests?
  - [ ] Manually
  - [ ] Component tests
- **What about code coverage?** Has code coverage gone up?
  - [ ] Code coverage increased
  - [ ] Code coverage decreased
  - [ ] Code coverage did not change
  - [ ] N/A
- **Were Integration tests executed?**
  - [ ] Starwars
  - [ ] Solo
  - [ ] N/A

---

## 🛠️ Code Quality
- **Did you review the output of SonarLint/SonarQube for your new code?**
  - [ ] Yes
  - [ ] No

---

## 📋 Functional Requirements
- **Did you do a “product” review for the ticket?** “Product” can be Product Owner/Designer/TL/Architect/CISO.
  - [ ] Yes
  - [ ] No
  - [ ] N/A

- **Was a risk analysis filled out?**
  - [ ] Yes
  - [ ] No

---

## 🚀 Deployment
- **Are there any manual release tasks that need to be executed as part of this story?** 
  - [ ] Yes
  - [ ] No
  - **If yes, did you create them?**
    - [ ] Yes
    - [ ] No

---

## 🔗 Dependencies
- **Are there any dependencies within or external to the team related to this task?** For example, a client change that requires a BE change or an integration with another team.
  - [ ] Yes
  - [ ] No
 
**Great job! 🎉 Your changes are ready to be merged into the main branch. Let's get this code into production! 🚀**