action
Github Actions for running CodSpeed in your CI (by CodSpeedHQ)
danger-js
⚠️ Stop saying "you forgot to …" in code review (by danger)
| action | danger-js | |
|---|---|---|
| 1 | 6 | |
| 17 | 5,177 | |
| - | 0.7% | |
| 7.4 | 8.2 | |
| 14 days ago | 7 days ago | |
| Shell | TypeScript | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
action
Posts with mentions or reviews of action.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-10-23.
-
Pinpoint performance regressions with CI-Integrated differential profiling
@codspeed/action, GitHub Action to run benchmarks and generate flame graphs
danger-js
Posts with mentions or reviews of danger-js.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-01-02.
-
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).
What are some alternatives?
When comparing action and danger-js you can also consider the following projects:
pytest-codspeed - Pytest plugin to create CodSpeed benchmarks
vscode-pull-request-github - GitHub Pull Requests for Visual Studio Code