vscode-pull-request-github
danger-js
| vscode-pull-request-github | danger-js | |
|---|---|---|
| 1 | 6 | |
| 2,199 | 5,168 | |
| 0.7% | 0.3% | |
| 9.7 | 8.2 | |
| 3 days ago | about 13 hours 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.
vscode-pull-request-github
-
Visual Studio Code April 2021
I do wish they would merge the work for GitHub Enterprise support. The work has been done it just needs merging, but for some reason they’re ignoring it. https://github.com/microsoft/vscode-pull-request-github/issues/1793
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).
What are some alternatives?
codestream - The Code Collaboration Tool Built for Remote Teams
lighthouse-ci - Automate running Lighthouse for every commit, viewing the changes, and preventing regressions
foam - A personal knowledge management and sharing system for VSCode
statoscope - Statoscope is a toolkit to analyze and validate webpack bundle
clippy-check - 📎 GitHub Action for PR annotations with clippy warnings
prcop - A Github action for linting Pull Requests.
Code-Server - VS Code in the browser
gitpod - The developer platform for on-demand cloud development environments to create software faster and more securely.
book-pr - Pull Requests and Code Review: Best Practices for Developers, from Junior to Team Lead.
use-force-update - React Hook to force your function component to update
semantic-pr-composer - Compose a pull request title and description based on a semantic branch name. Includes optional OpenAI integration
web-performance-research - Research in Web Performance