Dev Conventions
  • Dev Conventions
  • Git
    • Branch Flow
    • Conventional Commits
    • Pull requests template
    • Before making the PRs in typescript, keep in mind
  • Typescript
    • Introduction
    • Good practices
    • Solid
    • Using pnpm for Package Management
    • NestJs
    • NextJs
    • React
    • NestJs Testing
    • React Testing
    • Npm Registry
  • PYTHON
    • Introduction
    • Good practices
    • Testing
    • Naming Convention
  • DevOps
    • Introduction
    • Github Actions
    • Creating a Github Actions Workflow
  • Agile
    • Story Points
Powered by GitBook
On this page
  1. Git

Pull requests template


💡 This template provides a clear structure for describing the changes made in a Pull Request, ensuring that all important aspects are covered and facilitating the review by project collaborators.

# Checklist #
_Place an X in those options that apply_

- [ ] I checked that the branch follows the */sprint/{ feature | bugfix | testing | hotfix | release}*
- [ ] I checked that the branch and the commits contain the JIRA ID of the issue or feature
- [ ] I updated the corresponding documentation:
  - [ ] Notion
  - [ ] Gitbook
  - [ ] Other

# Description #
- {Corrects | implements | resolves } [ISSUE NAME (#issue-id)](#atlassian-issue-link)

## BREAKING CHANGES ##

- _(List the BREAKING CHANGES or write "None")_

# Tests performed #
_Place an X in those options that apply, ignore in case of documentation changes_

- [ ] I ran/updated unit tests
- [ ] Performed manual testing and verification
- [ ] Tried edge cases / bad data
- [ ] Tried UI/API Integration

## Remarks ##

* _(Observations to consider or appreciations)_

## Screenshots 📷 ##

_(Attach screenshot/s in case of changes in UI)_

[Learn Gitflow Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow)
PreviousConventional CommitsNextBefore making the PRs in typescript, keep in mind

Last updated 11 months ago