Skip to content

Latest commit

 

History

History
49 lines (34 loc) · 2.08 KB

File metadata and controls

49 lines (34 loc) · 2.08 KB

Contribute 🤝

  1. Make sure your branch is dev and sync with the remote branch.
  2. Create a new branch from the dev branch before start working on a new issue
  3. Get the git checkout -branch-name command from the JIRA kanban board
  4. Publish your branch
  5. When all the commits are ready for publishing, Create a Pull Request to the dev branch
  6. Make sure you are pulling 'from' your branch and pulling 'into' dev or immediate upstream branch
  7. Make sure to use the PULL request template with title and the description with your changes. (detailed)
  8. Review changes and Merge

Commit Message Types 💬

Commit message template

<type>[optional scope]:<description>

Example

style: update navbar hamburger drop down styles

  1. feat - Features - A new feature
  2. fix - Bug Fixes - A bug Fix
  3. docs - Documentation - Documentation only changes
  4. style - Styles - Changes that do not affect the meaning of the code
  5. refactor - Code Refactoring - A code change that neither fixes a bug nor adds a feature
  6. perf - Performance, Improvements - A code change that improves performance
  7. test - Tests - Addming missing tests or correcting existing tests
  8. build - Builds - Changes that affect the build system or external dependencies
  9. ci - Continuous Intergrations - Changes to our CI configuration files ans scripts
  10. chore - Chores Other changes that don't modify src or test files
  11. revert - Reverts Reverts a previous commit

References 📂

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

Learn to breack the UI into Components, Thinking in React

Learn React Hooks, Hooks

Learn JSX, JSX

Havarad CS50 React Session 2019, React CS50 Lecture 1

Havarad CS50 React Session Cont.. , React CS50 Lecture 2