(1 Kommentar) (0 Reaktionen) (1 zugewiesene Person)Elixir (113 Forks)batch import

T25mdocumentationelixirenhancementhelp wantedpriority-2technical

Repository-Metriken

Stars: (1.695 Sterne)
PR-Merge-Metriken: (Keine gemergten PRs in 30 T)

Beschreibung

Context

We have used 3rd party code quality badges e.g. CodeClimate in the past. But haven't applied them to our Elixir projects ... until now! 🤷‍♂️

Example

while reading: https://github.com/cesium/safira discovered via @ruilopesm & @nelsonmestevao 🫶

we see they have the following badge: prominently displayed:

The action is: /cesium/safira/.github/workflows/style.yml

Note: we are using credo in several projects e.g: mvp just not running the mix task on GitHub Actions or displaying a badge for "Code Quality".

Todo ✅

Document the setup steps in a code-style.md file in this (/learn-elixir) repo. 📝
- Create PR here in /learn-elixir 🆕
Add it to at least one repo, e.g: fields 🌻
Run the mix credo --all --strict on localhost to ensure it passes; 💻
- Make any necessary changes. 🛠️
Add a flat-square badge to the repo. 🏷️
Create PR in the repo where the style.yml task is being added. :shipit:
Submit for review. 👀

Contributor Guide

Research-Richtung: Untersuche den Beispiel GitHub Actions Workflow im cesium/safira Repository, um zu verstehen, wie mix credo in Elixir Projekten ausgeführt wird. Lerne, wie du ein Codequalitäts Badge zur README hinzufügst und überprüfe die mix.exs des Projekts auf die credo Konfiguration.
Tech Stack: elixirgithub actions
Domain: ci cdtooling
Issue Type: DevOps
Schwierigkeit: 2
Geschätzte Zeit: Halber Tag
Aktivitätsstatus: Aktiv
Klarheit: Klar
Voraussetzungen: GitElixir
Einsteigerfreundlichkeit: 75