Skip to content

Latest commit

Β 

History

History
139 lines (94 loc) Β· 3.41 KB

File metadata and controls

139 lines (94 loc) Β· 3.41 KB

What type of PR

(check all applicable)

target:

  • My pull request targets the development branch of the repository.
  • My pull request targets the production branch of the repository.

type:

  • πŸ• Feature
  • πŸ› Bug Fix
  • πŸ”₯ Hot Fix
  • πŸ“ Documentation Update
  • 🎨 Style
  • πŸ§‘β€πŸ’» Code Refactor
  • πŸ”₯ Performance Improvements
  • βœ… Test
  • πŸ€– Build
  • πŸ” CI
  • πŸ“¦ Chore
  • ⏩ Revert
  • πŸ“ͺ Release

Purpose

RESPONSE:

Approach

RESPONSE:

Where should the reviewer start?

RESPONSE:

Standards and style guidelines

I did ...

  • Run pre-commit hooks
  • Write readable and clean code
  • Write code following the established code style of the repository
  • Write precise and clear variables, functions and classes names
  • Create this PR with less than 800 LOC (lines of code)
  • Create this PR addressing a specific change (not many different things)
  • Use commit messages according to the defined standard
  • Put a descriptive title to this PR according to the defined standard

Quality assurance (mandatory)

I did ...

  • πŸ§ͺ run local scenarios
  • run the project locally and verify that there are no visible errors
  • βš™ deploy to dev environment and run without errors
  • πŸ”¬ create or update tests for my code
  • πŸ’£ run tests without errors or warnings
  • πŸ”Ž un data validations checking for:
    • duplicates
    • nulls
    • columns: names, data types
    • rows: count

Documentation

I create new documentation for...

  • πŸ‘©β€πŸ’» technical specs, in the repository
  • 🏒 users and business, in the documentation platform
  • πŸ“Š data (dictionaries, catalog)
  • πŸ™… nothing, no documentation needed

Technical debt

  • βœ… yes (explain what and why)
  • ❎ no

Post-deployment tasks

  • βœ… yes (explain what)
  • ❎ no

[optional] Learning

RESPONSE:

[optional] Emotion related GIF 😁

Commits

{{commit_messages}}