GitXplorerGitXplorer
m

commerce2.1

public
0 stars
0 forks
0 issues

Commits

List of commits on branch main.
Unverified
de954e5cf7d79f98fb844f07b1390d691e494738

fix: navigation revalidation error handling.

mmalewis5 committed a year ago
Unverified
f77e11d9f4a14353a8949400ecca1cd22700ba16

feat: add logs to diagnose potental RSC bug.

mmalewis5 committed a year ago
Unverified
1d696c07f82bf40b0b5fd058660b45d68784d376

fix: remove console.log

mmalewis5 committed a year ago
Unverified
ba6c81765cff6c61b0e38a016fd7cd6aa7616e0d

feat: add image priority support to page builder.

mmalewis5 committed a year ago
Unverified
df65187649dd966e1ed6272180f3b941066c95af

deps: v1.0.0

mmalewis5 committed a year ago
Unverified
5b1e860ebc53455c9e44bffc57431d980f299795

readme: update readme

mmalewis5 committed a year ago

README

The README file for this repository.

MatTech Commerce

Getting Started

Step 1: Clone this repository

git clone https://github.com/malewis5/commerce2.1.git

Step 2: Install dependencies

npm install

Step 3: Install Vercel CLI 

npm i -g vercel

Step 4: Link Vercel Project

  1. Configure the Vercel CLI
vercel login
  1. Follow the prompts to login with your credentials
  2. This command links your project with the remote Vercel project
vercel link

Step 5: Pull Environment Variables from Vercel

  1. This command pulls env variables from the project you linked. You can view them in the .env file created
vercel env pull

Step 6: Run local development server

npm run dev

Contributing

This project follows a CI/CD strategy that is outlined below. Please follow this strategy as it will be enforced. We enforce conventional commits and use release-please to generate release notes and changelog.

  1. Create your feature branch from main git checkout -b <ticket-number>-<description (optional)>.
  2. Write and test your code.
  3. When you're ready to commit, use the following convention for your commit message: <type>[optional scope]: <description> [optional body] [optional footer]
Type Use Case
fix patches a bug in your codebase and correlates with the patch version in semantic versioning
feat introduces a new feature to the codebase and correlates with a minor version in semantic versioning
BREAKING CHANGE! introduces a breaking API change and correlates with a major version in semantic versioning. A breaking change can be part of commits of any type indicated by a exclamation (!) e.g., a fix!: and feat!: types would be valid, in addition to any other type.
build Changes that affect the build system or external dependencies (example scopes: npm packages)
ci Changes to our CI configuration files and scripts
docs Documentation only changes
perf A code change that improves performance
refactor A code change that neither fixes a bug nor adds a feature
style Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
test Adding missing tests or correcting existing tests

This table is also available in the commit-template.md file

FOLLOWING THIS FORMAT IS CRITICAL FOR OUR RELEASE NOTES AND CHANGELOG

  1. This will create a preview deployment in Vercel where QA and UAT tasks will be completed. When the deployment is successful, the URL will be automatically added to the JIRA deployment on the ticket.