/handbook/react-best-practices/git-workflows/
What We Do
Digital Platform MigrationsKey SolutionsManaged ServicesStaffing SolutionsIndustriesProducts
Discovery
Strategic consultancy & project roadmap
Growth Services
On demand development & consultation
Site Maintenance
Annual maintenance. Done for you
QE Services
Testing across SDLC for assured quality
Hosting Migration
Move to a performant hosting with zero downtime
WooCommerce
Enterprise commerce delivered without lock-in
AI
Unlock real use cases and integrations
All Services
A suite of services for any need
Technology STACK
eCommerce
Scale your e-commerce with WooCommerce, integrations, and custom extensions for growth.
EasyEngine
Server management tool that makes using WordPress on Nginx easy.
Web Auditor
Performance Audit & Insights for your Website.
rtMedia
A complete media management plugin for WordPress.
Resources
About Us
CLEAR
Resources React project best practices Commit messages
Topics
On this page
- React project best practices
- Project structure
- State management
- Component architecture
- Styling
- Hooks
- Performance optimization
- Commit messages
- Code quality
- Data loading
- Testing
- Dependency management
- Accessibility
- React frameworks
- Documentation
- Deployment and monitoring
- React skeleton
- Appendices
1. Be concise yet descriptive
2. Use imperative mood
3. Add context in the body (optional)
Bad commit messages: ❌
PR titles
Keep it short and focused
Include context or scope
Avoid abbreviations and jargon
Common formats
Example of bad PR titles ❌
PR description
Git branch naming
Last updated on Apr 2, 2026
Commit messages
While commit messages are not React-specific, they are crucial for maintaining a clean and understandable project history. Clear commit messages and PR conventions improve collaboration, make debugging easier, and speed up code reviews.
As we currently lack a general best practices guide, these guidelines will serve as a placeholder and can be moved to the broader document when available.
1. Be concise yet descriptive
- The subject line should summarize the change in 50 characters or less.
- Avoid vague phrases like “fixed stuff” or “updated code.”
2. Use imperative mood
When writing commit messages, use the imperative mood. This means phrasing the subject line as if you’re giving a command. This style aligns with Git’s approach because commit messages describe what applying the commit will do, not what has been done.
A well-formed Git commit subject line should complete this sentence
“If applied, this commit will…”
- ✅ Add unit tests for login functionality
- ❌ Added unit tests for login functionality
3. Add context in the body (optional)
If the change is complex, include a brief explanation in the body.
- What was changed and why.
- Mention trade-offs or limitations..
- Include bullet points for better readability.
- Reference related issues in the footer (e.g., Closes #123).
Example
Resolve crash when editing user details
- Fix null reference error when editing without selecting a role
- Add default role assignment for new users
Closes #123
Other Points:
- Capitalize the subject line.
- Do not end the subject line with a period.
Bad commit messages: ❌
Too vague: These messages are too generic and don’t describe what was changed, why, or where.
- Fixed stuff
- Made changes
- Update code
- Bug fixed
- fixed: login
Too long: Commit messages should be concise. This message is overwhelming and doesn’t follow the 50-character rule for the subject line.
- ❌ Refactored the entire codebase to improve performance by rewriting major parts of the backend authentication module and fixing various bugs in the process while also updating the documentation for developers.
Unprofessional: These messages are unprofessional and provide no meaningful information about the commit.
- Fixing this for the last time, I swear
- I have no idea why this works but okay
Written in the future tense: Commit messages describe what was done, not what will be done. Future tense is misleading and unnecessary.
- Will add new login feature
- Will fix logout issue
Commit examples from some known developers to us
PR titles
When writing PR titles, we follow most of the same principles used for writing good commit subject lines. Specifically, we aim to:
- Be concise yet descriptive.
- Use an imperative mood.
- Capitalize the subject line.
- Avoid ending the subject line with a period
Example
✅ Fix crash on login page when username is empty
Additional consideration for PR titles are as follows
Keep it short and focused
Limit to 50-70 characters if possible and provide additional details in the PR description, not the title.
Example
✅ Refactor user profile component for better readability
❌ Refactored the entire user profile component and removed old code for improved readability and maintainability
Include context or scope
Mention the area of the codebase or feature the PR affects.
Example
✅ Update API response handling for payment gateway
❌ Update API response handling
Avoid abbreviations and jargon
Use plain language to ensure clarity.
Example
✅ Improve error handling for user registration API
❌ Fix ERR#123 in reg API
Common formats
We may follow the following formats for better clarity to some PR titles.
[Type/Action/Area/Feature]: [Feature/Change/Issue]
- Feature: Add user authentication flow
- Fix: Resolve issue with image upload failing on iOS
- Refactor: Optimize database queries for faster load times
- Login Page: Fix typo in error message
- Dashboard: Add filter for user roles
Avoid using format prefixes when not required
Don’t use structured prefixes (like Feature, Fix, etc.) if they don’t add clarity to the PR title. Instead, focus on making the title concise, human-readable, and reflective of the PR’s purpose. While structured formats such as [Type/Action/Area/Feature] can make PR titles more consistent, forcing them for every PR can lead to redundancy, confusion, or bloated titles. Sometimes, a straightforward, human-readable title works better.
Examples
Trivial or minor changes: Some changes are too small to warrant a structured format.
Bad (Unnecessary Prefix): ❌
- Refactor: Remove unused import
- Feat: Fix typo in a comment
- Fix: Update README formatting
- Refactor: Update .gitignore
Multi-area or cross-cutting changes: If the PR spans multiple unrelated areas, using a prefix can mislead reviewers into thinking the change is scoped to a single area.
Bad (Unnecessary Prefix): ❌
- Feat: Update dashboard and fix login flow
- Fix: Change settings and update database schema
Example of bad PR titles ❌
- Changes made (Generic title)
- Improve performance (Ambiguous title)
- Updated the user profile page and fixed a bug that caused the app to crash when users clicked on the save button while editing their profile, and also improved performance on the settings page. (Too long)
- Add info tab to Bottom table ( Improper capitalization )
PR description
A Pull Request description should not be written in the past tense because it describes the current state of the PR, it represents changes that are being proposed, reviewed, and merged, rather than something already completed or finalized. Therefore it should be written in a declarative tone for example
- ✅ This PR adds user authentication functionality to enable secure logins using OAuth2
- ❌ Added user authentication functionality.
We should create a template for PR description as per the need of the project. Here is our preferred PR template.
## Description
<!-- What do we want to achieve with this PR? -->
## Relevant Technical Choices
<!-- For Code Reviewers: Please describe your changes. -->
## Testing Instructions
<!-- For someone doing QA: How can the changes in this PR be tested? Please provide step-by-step instructions to test the changes. -->
## Additional Information:
<!-- Include any other context, links, or references that reviewers or QA should be aware of. -->
## Screenshot/Screencast
<!-- Add visual aids to demonstrate the changes made in this PR, if applicable. -->
## Checklist
<!-- Check these after creating PR, use NA if something is not applicable -->
- [ ] I have carefully reviewed the code before submitting it for review.
- [ ] This code is adequately covered by unit tests to validate its functionality.
- [ ] I have conducted thorough testing to ensure it functions as intended.
- [ ] A member of the QA team has reviewed and tested this PR (To be checked by QA or code reviewer)
<!--
Example:
Fixes #123
Partially addresses #22
See #834
-->
Fixes #
Git branch naming
To maintain consistency and clarity across the team, we follow these rules for naming Git branches:
1. Use a clear and consistent structure
Adopt a structured format to make branch names meaningful and easy to understand. A common structure is:
[type]/[short-description]
2. Use lowercase letters only
Examples:
- ✅ feat/add-user-auth
- ✅ fix/login-issue
3. Use hyphens to separate words
Examples:
- ✅ feat/add-user-auth
- ❌ feat_add_user_auth
4. Begin with a prefix for the branch type
feat/: New featuresfix/: Bug fixesref/: Refactors (no behavior change)chore/: Non-functional tasks (dependencies, configs)docs/: Documentation changestest/: Adding or modifying testsrelease/: Preparing a release (e.g.,release/v0.2.1)perf/: Performance improvementsrevert/: Reverting commitssecurity/: Security patchestry/: Experimental work, not for mergingadd/: Introducing small files/components/assets
Things to avoid:
-
Use a brief yet descriptive name
- Do: feat/add-search-bar
- Avoid: feat/added-a-new-search-bar-that-works-with-filters
-
Avoid special characters
- Do: docs/update-readme
- Avoid: docs/update@readme
-
Avoid redundant information
- Do: fix/logout-crash
- Avoid: fix/logout-crash-task
Performance optimization
PREVIOUS
Credits
Sayed Taqui
Author
Sayed Taqui
Author
Seasoned React, JavaScript, and WordPress Developer. Contributed significantly to WordPress Core. Currently serving as the Lead WordPress Engineer at rtCamp. Passionate about crafting innovative so…
Imran Sayed
Author
Imran Sayed
Author
Senior Software Engineer and Full-Stack Web Developer building high-performance, user-centric web applications that drive business growth. Expertise lies in e-commerce development, custom WordPress…
Ayush Nirwal
Author
Ayush Nirwal
Author
Amoghavarsha Kudaligi
Author
Amoghavarsha Kudaligi
Author
Mayank Rana
Author
Mayank Rana
Author
Good Work. Good People.
Industry partnerships
Compliance certifications
United States India
© rtCamp Inc. since 2009. All rights reserved.
Terms of Service · Privacy Policy · Trust Center
Company
Solutions
Subscribe to our newsletter and get a few email updates every month.
United States India
© rtCamp Inc. since 2009. All rights reserved.
Terms of Service · Privacy Policy · Trust Center
Cookie Consent
We value your privacy
We use cookies to give you the best possible experience. By clicking “Accept,” you consent to our use of cookies to improve site functionality, analyze usage, and personalize content and communications. Your privacy matters to us, and we are committed to handling your data responsibly and transparently. Please check our Privacy Policy for more details.
Manage PreferencesDon’t AllowAllow All
Why do we use cookies?
×
By clicking "Accept" or "Decline All" at the bottom, you consent to the use of cookies and other tools as described in our Cookie Policy in accordance with your settings and accept our Terms of Service.
Toggle EssentialEssential
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Geolocation Config
This cookie is used to store the consent settings based on the visitor's location.
30 days
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
30 days
Toggle CloudFlareCloudFlare
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
Service URL: developers.cloudflare.com (opens in a new window)
Name
Description
Duration
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
Toggle CommentsComments
These cookies are needed for adding comments on this website.
Name
Description
Duration
comment_author
Used to track the user across multiple sessions.
Session
comment_author_email
Used to track the user across multiple sessions.
Session
comment_author_url
Used to track the user across multiple sessions.
Session
Toggle GodamGodam
GoDAM" is primarily a specialized WordPress plugin and media management service designed to enhance video hosting, marketing, and asset management directly within the WordPress dashboard.
Service URL: godam.io (opens in a new window)
Name
Description
Duration
user_image
Temporarily stores the path to the user's avatar or profile picture for quick rendering in the website header.
session
user_id
Stores the numerical ID of the logged-in user to maintain session continuity and basic site operations.
session
full_name
Stores the logged-in user's display name to personalize the site interface without needing database queries.
session
system_user
First-party cookie used to store basic application state identifying the current system user role.
session
sid
A generic session ID cookie used to maintain user state and functionality as the visitor navigates through the site.
session
Toggle Google reCAPTCHAGoogle reCAPTCHA
Google reCAPTCHA helps protect websites from spam and abuse by verifying user interactions through challenges.
Name
Description
Duration
_GRECAPTCHA
Google reCAPTCHA sets a necessary cookie (_GRECAPTCHA) when executed for the purpose of providing its risk analysis.
179 days
Toggle Google Tag ManagerGoogle Tag Manager
Google Tag Manager simplifies the management of marketing tags on your website without code changes.
Name
Description
Duration
cookiePreferences
Registers cookie preferences of a user
2 years
td
Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
session
Toggle StatisticsStatistics
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Toggle Factors AIFactors AI
Factors.ai is a B2B account intelligence and marketing analytics platform that helps Go-To-Market (GTM) teams identify anonymous website visitors, track buyer journeys, and measure the ROI of marketing campaigns.
Service URL: www.factors.ai (opens in a new window)
Name
Description
Duration
_fuid
It is sent to capture session details and track user behavior across your website to provide behavioral data and intent signals.
1 Year
Toggle Google AnalyticsGoogle Analytics
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Service URL: policies.google.com (opens in a new window)
Name
Description
Duration
FPGSID
Stores a session or user identifier to track how visitors interact with a website. This helps Google Analytics measure website performance, user engagement, and usage patterns.
Session
FPLC
Used by Google Analytics to link visitor interactions and sessions across multiple related domains.
20 hours
FPID
A server-side Google Analytics cookie used as an alternative user identifier when third-party cookies are restricted.
2 years
_ga
ID used to identify users
2 years
_ga_
ID used to identify users
2 years
Toggle Jetpack StatsJetpack Stats
Jetpack's built-in visitor analytics. It records page views, referring sites, search terms, and outbound link clicks, and also carries the shared visitor-tracking library used by Jetpack Instant Search and WooCommerce Analytics.
Service URL: automattic.com (opens in a new window)
Name
Description
Duration
tk_aip
Stores a list of anonymous visitor IDs so they can be merged into one identity once a visitor is recognized.
Up to 5 years
tk_tc
Used once per page load to work out which cookie domain the Tracks library should use, then removed as soon as it's read back.
Session (deleted immediately after use)
tk_qs
Queues analytics events for Jetpack's Tracks library so none are lost if the page closes before they can be sent.
30 minutes
tk_ai
Stores a randomly-generated anonymous visitor ID so Jetpack's Tracks analytics library can link tracking events to the same visitor.
Session in wp-admin; up to 5 years on the frontend
Toggle Microsoft ClarityMicrosoft Clarity
Clarity is a web analytics service that tracks and reports website traffic.
Service URL: clarity.microsoft.com (opens in a new window)
Name
Description
Duration
CLID
Identifies the first-time Clarity saw this user on any site using Clarity.
12 months
ANONCHK
Indicates whether MUID is transferred to ANID, a cookie used for advertising. Clarity doesn't use ANID and so this is always set to 0.
Session
_clck
Persists the Clarity User ID and preferences, unique to that site is attributed to the same user ID.
12 months
_clsk
Connects multiple page views by a user into a single Clarity session recording.
12 months
Toggle Parse.lyParse.ly
Parse.ly is a content analytics platform that helps publishers optimize audience engagement and content performance.
Name
Description
Duration
cookies.js_dtest
This cookie determines whether the browser accepts cookies.
session
_parsely_session
JSON document storing information identifying a browsing session according to Parsely’s proprietary definition
30 minutes
_parsely_visitor
JSON document uniquely identifying a browser and counting its sessions
13 months
Toggle SalespanelSalespanel
Salespanel is a B2B marketing and sales software that identifies, tracks, and qualifies website visitors and leads in real-time using first-party data. It helps businesses monitor customer journeys, score leads based on behavior, and syncs this data with CRMs (like Pipedrive or HubSpot) to improve conversion rates.
Service URL: salespanel.io (opens in a new window)
Name
Description
Duration
track_uid
Identify and tracking a lead
12 moths
Toggle MarketingMarketing
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Toggle Bing / MicrosoftBing / Microsoft
Bing, powered by Microsoft, is a search engine providing web, image, video, and map search capabilities.
Name
Description
Duration
MR
Used to collect information for analytics purposes.
6 months
ANONCHK
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
10 minutes
SM
Used by Microsoft in synchronizing the MUID across multiple Microsoft domains to track users for advertising.
session
MUID
Identifies unique web browsers visiting Microsoft sites. These cookies are used for advertising, site analytics, and other operational purposes.
1 year
Toggle DoubleClick/Google MarketingDoubleClick/Google Marketing
A comprehensive digital advertising platform for managing campaigns, optimizing performance, and analyzing audience data.
Name
Description
Duration
IDE
This cookie is used for targeting, analyzing and optimisation of ad campaigns in DoubleClick/Google Marketing Suite
2 years
ar_debug
Store and track conversions
Persistent
Toggle LinkedInLinkedIn
LinkedIn is a professional networking platform for job seekers, employers, and industry connections.
Name
Description
Duration
bscookie
Used by LinkedIn to track the use of embedded services.
1 year
AnalyticsSyncHistory
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries
30 days
bcookie
Used by LinkedIn to track the use of embedded services.
1 year
li_sugr
Used to make a probabilistic match of a user's identity outside the Designated Countries
90 days
lidc
Used by the social networking service, LinkedIn, for tracking the use of embedded services.
1 day
UserMatchHistory
Used by LinkedIn Ads to synchronize and match user IDs across different ad networks and data providers.
30 days
Toggle LinkedIn InsightLinkedIn Insight
LinkedIn Insight is a web analytics service that tracks and reports website traffic.
Service URL: www.linkedin.com (opens in a new window)
Name
Description
Duration
li_sugr
Used to make a probabilistic match of a user's identity.
90 days
lidc
Used for routing and session management.
24 hours
Toggle LiveIntentLiveIntent
LiveIntent provides a platform for email advertising and identity-driven marketing solutions.
Name
Description
Duration
_lc2_fpi_js
Companion cookie to _lc2_fpi used by JavaScript to facilitate cross-domain ad tracking and user identification.
1 year
_lc2_fpi
First-party tracking cookie usually associated with LiveRamp to identify users across devices for targeted advertising.
1 Year
_li_ss
Sets a unique ID for the visitor, that allows third party advertisers to target the visitor with relevant advertisement. This pairing service is provided by third party advertisement hubs, which facilitates real-time bidding for advertisers.
1 month
lidid
Collects data on visitors' behaviour and interaction - This is used to make advertisement on the website more relevant. The cookie also allows the website to detect any referrals from other websites.
2 years
Toggle Cookie PolicyCookie Policy
You can find more information in our Privacy Policy.
Allow AllDecline All
Accept