Closed arpitkuriyal closed 4 weeks ago
We require all PRs to follow Conventional Commits specification. More details 👇🏼
No release type found in pull request title "solve the issue of DOM property warning". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/
Available types:
- feat: A new feature
- fix: A bug fix
- docs: Documentation only changes
- style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- refactor: A code change that neither fixes a bug nor adds a feature
- perf: A code change that improves performance
- test: Adding missing tests or correcting existing tests
- build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
- ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
- chore: Other changes that don't modify src or test files
- revert: Reverts a previous commit
Built without sensitive environment variables
Name | Link |
---|---|
Latest commit | 6a2269650a0c64e26545d37b0d90d3b40dfd61f7 |
Latest deploy log | https://app.netlify.com/sites/peaceful-ramanujan-288045/deploys/671a7f3ad8fc25000813cc0d |
Deploy Preview | https://deploy-preview-440--peaceful-ramanujan-288045.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Description