danger-js
gradle-build-action
Our great sponsors
| danger-js | gradle-build-action | |
|---|---|---|
| 6 | 2 | |
| 5,161 | 645 | |
| 0.6% | 1.6% | |
| 8.2 | 9.3 | |
| 2 days ago | 4 days ago | |
| TypeScript | TypeScript | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
danger-js
-
Enforcing ESLint rules: A guide to taming codebase chaos
Make sure to not accept any Pull Request with commented ESLint errors to ensure a continuous improvement of your codebase quality. Some tools can help you to automate this part of the review, such as Danger JS.
-
How We Started Managing BSA Delivery Processes on GitHub
commitlint & dangerjs. Linters that help maintain consistency in all user-provided information related to Git and GitHub (commits, branch names, PR titles, etc.).
- DangerJS – automate common code review chores
- PRcop – open-source Pull Request linter for Github Actions built with JS
-
How to deal with teammates forcing personal preference into code reviews and nit picking everything?
Does your team use any automatic code formatting or linting tools? E.g. for TypeScript or JavaScript, a combination of Prettier and ESLint, with a well understood and agreed-upon configuration, can avoid this kind of back and forth. Danger.js is a good way to handle the higher level concerns that cannot be addressed at the syntax level.
-
React PWA Performance Study Case
This tool is run in our CI pipeline for every PR and the result is shown in the Github PR (it uses Danger behind it).
gradle-build-action
- how to access Gradle scans and other build outputs with one click from a pull request
-
Tips how to speed up KotlinJS compilation?
Build & Configuration cache probably won't help much in continuous mode. They will help when re-running tasks after switching branches, and on CI builds - especially when the Gradle caches can be re-used across builds (e.g. by using https://github.com/gradle/gradle-build-action/ on GitHub).
What are some alternatives?
vscode-pull-request-github - GitHub Pull Requests for Visual Studio Code
vscode-spotless-gradle - A VS Code extension to lint & format your source files using Spotless & Gradle.
lighthouse-ci - Automate running Lighthouse for every commit, viewing the changes, and preventing regressions
wrapper-validation-action - Gradle Wrapper Validation Action
statoscope - Statoscope is a toolkit to analyze and validate webpack bundle
monorepo.tools - Your defacto guide on monorepos, and in depth feature comparisons of tooling solutions.
prcop - A Github action for linting Pull Requests.
github-pages-deploy-action - 🚀 Automatically deploy your project to GitHub Pages using GitHub Actions. This action can be configured to push your production-ready code into any branch you'd like.
gitpod - The developer platform for on-demand cloud development environments to create software faster and more securely.
actions-gh-pages - GitHub Actions for GitHub Pages 🚀 Deploy static files and publish your site easily. Static-Site-Generators-friendly.
use-force-update - React Hook to force your function component to update
Gradle - Adaptable, fast automation for all