multi-gitter
reviewdog
multi-gitter | reviewdog | |
---|---|---|
12 | 12 | |
770 | 7,385 | |
- | 1.1% | |
8.8 | 9.5 | |
3 days ago | about 20 hours ago | |
Go | Go | |
Apache License 2.0 | 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.
multi-gitter
-
Any tool for committing the same change across multiple repos?
Sounds similar to multi-gitter https://github.com/lindell/multi-gitter
-
Force stage in pipeline
It's not necessarily enforcement like the compliance pipeline but I use Multi-gitter to check if our compliance.yml is an entry in the include portion of the ci yaml file. If it's not detected it raises a MR to add it. I think this workflow would work pretty well for you too.
-
5 innovative dev tools to improve your workflow
Multi-gitter - Run scripts across Git repos.
- multi-gitter
-
Mu-repo – A tool to help working with multiple Git repositories
Yesterday I posted about multi-gitter (https://github.com/lindell/multi-gitter), but I've since found mu-repo much I much prefer. Really is fantastic for managing a large number of repos you need to perform operations on. It's lightweight and simple.
- Multi-gitter – CLI to update multiple Git repositories in bulk
-
Goodbye interface{}, Hello any
If you have a lot of repositories, in for example a GitHub org, you can do this for all of them with multi-gitter.
-
Git-Xargs
This is very similar to a project I created around a year ago. https://github.com/lindell/multi-gitter
Multi-gitter does also have support for other source control systems, and from what I can gather, does in general have more configuration options. But I will definitely take a look at the differences and take inspiration.
- multi-gitter, a tool that enables changes over multiple repositories at once, just released Gitea support
- Show HN: multi-gitter – Update multiple repositories in bulk
reviewdog
-
Code reviews and Suggestions from SARIF report
I build a general converter from SARIF to Reviewdog Diagnostic Format (RDFormat), then use Reviewdog to give suggested code changes as well as the context of the changes for PR reviewing.
-
My CNCF LFX Mentorship Spring 2023 Project at Kubescape
I helped improve the Kubescape GitHub Actions fix suggestions code review process, where I created the workflow which works by collecting the SARIF (Static Analysis Results Interchange Format) file that kubescape generates. Then, with the help of HollowMan6/sarif4reviewdog, convert the SARIF file into RDFormat (Reviewdog Diagnostic Format) and generate reviews for code fix suggestions on GitHub Actions using Reviewdog. I also helped add the “fix" object support for the Kubescape-generated SARIF report.
- Reviewdog: Code analysis regardless of programming language
-
Goast: Generic static analysis for Go Abstract Syntax Tree by OPA/Rego
Static analysis should be performed continuously by CI (Continuous Integration) to prevent unintentional inclusion of code. The JSON output schema is compatible with reviewdog and can be used as is in reviewdog.
-
reviewdog-gitlab-webhook: Trigger reviewdog checks for GitLab repo using webhooks
Trigger reviewdog checks on a repository via GitLab webhook rather than CI job.
-
How to reuse steps in Tekton tasks
# parameters - op: add path: /spec/params/- value: name: report-file default: reportfile description: Report file with errors - op: add path: /spec/params/- value: name: format default: golint description: Format of error input from the task - op: add path: /spec/params/- value: name: reporter default: local description: Reporter type for reviewdog https://github.com/reviewdog/reviewdog#reporters - op: add path: /spec/params/- value: name: diff default: git diff FETCH_HEAD description: Diff command https://github.com/reviewdog/reviewdog#reporters # workspaces - op: add path: /spec/workspaces/- value: name: token description: | Workspace which contains a token file for Github Pull Request comments. Must have a token file with the Github API access token # steps - op: add path: /spec/steps/- value: name: reviewdog-report image: golangci/golangci-lint:v1.31-alpine # both have the same workspace name workingDir: $(workspaces.source.path) script: | #!/bin/sh set -ue wget -O - -q https://raw.githubusercontent.com/reviewdog/reviewdog/master/install.sh | sh -s -- -b $(go env GOPATH)/bin export REVIEWDOG_GITHUB_API_TOKEN=$(cat $(workspaces.token.path)/token) cat $(params.reportfile) | reviewdog -f=$(params.format) -diff="$(params.diff)"
-
I manage my dev.to blog in GitHub repository
In reference article, use prettier to format the markdown and the code snippets. I implement a text review using textlint and reviewdog in addition to that.
-
Automated code review for on-prem
JetBrains Qodana is one option, but currently requires glue code to map the findings to MR comments. I'm using reviewdog for it but I'm hoping they'll eventually fix it to have native integration
-
GitHub Action to annotate tsc errors;
I'm trying to make a GitHub action which automatically runs tsc to find TypeScript errors. Those errors should be annotated inline in the PR/Commits. I found reviewdog, which should work perfectly for this - but I played around with that for about 4 hours now and can't seem to get it to report errors successfully. tsc exits with code 2, but reviewdog still says that everything went fine. So I'm trying to find another solution for this, has anyone here done this before? For comparison, I managed to do the same thing with ESLint by adding a custom formatter to the eslint command (-f param), which then gets automatically picked up by the GitHub action - but I can't find something similar for tsc..
-
Incident with GitHub Actions, Issues, Pull Requests, and Webhooks
I used ReviewDog to wire in Qodana results, so I hear you about wishing it was built in, but it is achievable: https://github.com/reviewdog/reviewdog#reporter-gitlab-merge...
Based on my contact with GitLab's built-in other scanning tools, I wouldn't trust their vuln management further than I could throw it, so you're likely not missing much on that front
What are some alternatives?
gitupdate - Commit and push updated files with file names as commit message
Qodana - 📝 Source repository of Qodana Help
glab - The GitLab CLI tool. Archived: now officially adopted by GitLab as the official CLI tool and maintained at https://gitlab.com/gitlab-org/cli. See https://github.com/profclems/glab/issues/983
prettier - Prettier is an opinionated code formatter.
ghorg - Quickly clone an entire org/users repositories into one directory - Supports GitHub, GitLab, Bitbucket, and more 🥚
datree - Prevent Kubernetes misconfigurations from reaching production (again 😤 )! From code to cloud, Datree provides an E2E policy enforcement solution to run automatic checks for rule violations. See our docs: https://hub.datree.io
mu-repo - Tool to help in dealing with multiple git repositories
kube-score - Kubernetes object analysis with recommendations for improved reliability and security. kube-score actively prevents downtime and bugs in your Kubernetes YAML and Charts. Static code analysis for Kubernetes.
gitman - A simple yet powerful opinionated tool for managing GitHub repositories.
ls-lint - An extremely fast directory and filename linter - Bring some structure to your project filesystem
gut - An alternative git CLI for Windows, macOS, and Linux
editorconfig-vim - EditorConfig plugin for Vim