Scribd
Upload
19 views2 pages

FREFIX

The document outlines various commit message prefixes used in version control. Each prefix indicates a specific type of change, such as 'feat' for new features, 'fix' for bug fixes, and 'docs' for documentation updates. It also includes guidelines for using prefixes like 'temp' for temporary commits and 'ci' for continuous integration changes.

Uploaded by

oxa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
19 views2 pages

FREFIX

The document outlines various commit message prefixes used in version control. Each prefix indicates a specific type of change, such as 'feat' for new features, 'fix' for bug fixes, and 'docs' for documentation updates. It also includes guidelines for using prefixes like 'temp' for temporary commits and 'ci' for continuous integration changes.

Uploaded by

oxa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

Commit Message Prefixes

1. feat: Use when adding a new feature.


feat: add responsive navbar
feat: implement about us page layout

2. fix: Use for bug fixes.


fix: correct header alignment on mobile
fix: resolve issue with contact form submission

3. style: Changes that do not affect the functionality (formatting, spacing, etc.).
style: update footer text color
style: reformat code in Home.js

4. refactor: Code refactoring without changing functionality.


refactor: optimize Navbar component
refactor: clean up App.js structure

5. perf: Improve performance.


perf: lazy load images on homepage
perf: reduce bundle size by optimizing dependencies

6. docs: Documentation changes.


docs: add README installation instructions
docs: update component documentation

7. test: Adding or fixing tests.


test: add unit tests for ContactForm component
test: fix broken tests for About page

8. chore: Routine tasks, maintenance, or project setup.


chore: update dependencies
chore: configure ESLint

9. build: Changes that affect the build system or external dependencies.


build: add webpack configuration
build: set up CI/CD pipeline

10. ci: Continuous integration and deployment changes.


ci: configure GitHub Actions
ci: add deployment script

10. revert: Revert a previous commit.


revert: undo feature addition of service section

11. temp: Temporary commits for experimentation (use sparingly).


temp: test layout changes in Navbar
temp: experiment with color palette

Commit Message Prefixes


1. feat: Use when adding a new feature.
2. fix: Use for bug fixes.
3. style: Changes that do not affect the functionality (formatting, spacing, etc.).
4. refactor: Code refactoring without changing functionality.
5. perf: Improve performance.
6. docs: Documentation changes.
7. test: Adding or fixing tests.
8. chore: Routine tasks, maintenance, or project setup.
9. build: Changes that affect the build system or external dependencies.
10. ci: Continuous integration and deployment changes.
11. temp: Temporary commits for experimentation (use sparingly).

You might also like