danger-js
architecture_decision_record
Our great sponsors
danger-js | architecture_decision_record | |
---|---|---|
6 | 22 | |
5,148 | 11,137 | |
0.4% | - | |
7.5 | 7.9 | |
about 1 month ago | 17 days ago | |
TypeScript | ||
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).
architecture_decision_record
-
Ask HN: How to Translate Markdown Repositories?
I'm translating the Architecture Decision Record project to more languages. I'm seeking advice and guidance please: how are you all managing translations of git repos of content such as documentation and markdown files?
My experiments so far are here:
https://github.com/sixarm/locale-help
My work-in-progress is to create a top level directory `./locales`, then subdirectories per language using a ISO 639-1 two-letter language code, then content directories, for example:
./locales/en/hello/ (this is in English)
./locales/es/hola/ (this is in Español a.k.a. Spanish)
What do you use to track which content directories correspond to each other across languages?
The Architecture Decision Record repo is now mostly auto-translated into Spanish, French, Welsh, and Korean, in the top level directory `./locales`, using the program `slug-case` to help translate the markdown content file headlines into directory names:
https://github.com/joelparkerhenderson/architecture-decision-record
- Show HN: Architecture Decision Record – Spanish Tranlsations
-
Architecture diagrams enable better conversations
Hi, article author here, we supplement our architecture diagrams with Architectural Decision Records (ADRs) https://github.com/joelparkerhenderson/architecture-decision... in the ADR we capture:
-
Documenting your decisions using the ADR approach
Architecture decision record by joelparkerhenderson
-
Polar v1.0: Let’s Fix Open Source Funding
If anyone wants to see Polar in action on a GitHub issue, I'm experimenting with Polar on my Architecture Decision Record repo:
https://github.com/joelparkerhenderson/architecture-decision...
(I'm on the fence about the value of Polar for this kind of issue... see what you think)
-
How did you acquire confidence in system design?
This method is only slightly formalized as ADR (architecture decision record). What I personally like about templates that people share on the interned (https://github.com/joelparkerhenderson/architecture-decision-record) it that if force designed to actually consider cons of selected approach or honestly attempt to analyze alternatives.
-
A practical overview on Architecture Decision Records (ADR)
The GitHub repo joelparkerhenderson/architecture-decision-record is a good source to get an overview of tools, articles and examples.
-
Ask HN: How to do Git successors, in case of death?
GitHub is prompting me to add a git successor to my open source repo, in case I die.
Do people here have advice about how to do this, or experience in doing it?
Any brainstorms about how to do it across all the related repos, orgs, etc., such as a will, or well-known file in the repo, that donates to a nonprofit, or foundation, etc.?
Here's the repo:
https://github.com/joelparkerhenderson/architecture-decision-record
-
A Simple Framework for Architectural Decisions
Architecture Decision Records are a big help for teamwork. I have a bunch of notes and examples here, including from my time at ThoughtWorks with technology radars.
https://github.com/joelparkerhenderson/architecture-decision...
-
Documenting agreements
If you want to get started with ADR, I recommend looking at the repository, where you can find different ADR templates and examples of how to use them.
What are some alternatives?
vscode-pull-request-github - GitHub Pull Requests for Visual Studio Code
backstage - Backstage is an open platform for building developer portals
lighthouse-ci - Automate running Lighthouse for every commit, viewing the changes, and preventing regressions
oasis-core - Performant and Confidentiality-Preserving Smart Contracts + Blockchains
statoscope - Statoscope is a toolkit to analyze and validate webpack bundle
architecture-decision
prcop - A Github action for linting Pull Requests.
rfcs - Specifications for Interledger and related protocols
gitpod - The developer platform for on-demand cloud development environments to create software faster and more securely.
arc42.org-site - (jekyll-based) website for arc42.org - the template for communicating software architectures.
use-force-update - React Hook to force your function component to update
log4brains - ✍️ Log and publish your architecture decisions (ADR)