Skip to content

Commit 9639266

Browse files
docs(standards): add make fix blog post and update intro post
New blog post announcing make fix auto-remediation and CI-based mirror automation. Update intro post to reflect make fix is shipped. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1 parent 673f0e2 commit 9639266

File tree

2 files changed

+37
-1
lines changed

2 files changed

+37
-1
lines changed

content/blog/2026-03-02-introducing-devrail.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ See the [agent setup guide](/docs/getting-started/agents/) for detailed configur
7878

7979
DevRail is in **beta**. The core contract -- Makefile, container, `.devrail.yml` -- is stable and used in production projects. Language support for all seven ecosystems ships in the `v1` container image. Standards, tool versions, and defaults may still change based on real-world usage.
8080

81-
What works today: new projects from templates, retrofitting existing repos, CI integration, agent instruction files. What's still evolving: the `make fix` auto-remediation workflow, additional language ecosystems, and edge cases we haven't hit yet.
81+
What works today: new projects from templates, retrofitting existing repos, CI integration, agent instruction files, and `make fix` auto-remediation. What's still evolving: additional language ecosystems and edge cases we haven't hit yet.
8282

8383
If you run into problems or have opinions about how things should work, [open an issue](https://github.com/devrail-dev/devrail.dev/issues). Bug reports, feature requests, and "this default is wrong" complaints are all welcome.
8484

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
title: "make fix and Mirror Automation"
3+
date: 2026-03-03
4+
description: "Auto-remediation lands for all seven language ecosystems, and CI-based mirroring eliminates manual git push between GitLab and GitHub."
5+
---
6+
7+
Two features shipped today: `make fix` for auto-remediation and CI-based mirror automation between GitLab and GitHub.
8+
9+
## make fix
10+
11+
`make check` tells you what's wrong. `make fix` fixes what it can.
12+
13+
```console
14+
$ make fix
15+
✓ python (ruff format, ruff check --fix)
16+
✓ bash (shfmt -w)
17+
✓ go (gofumpt -w)
18+
✓ js/ts (prettier --write, eslint --fix)
19+
```
20+
21+
The target runs formatters and auto-fixable linter rules in-place for all seven supported language ecosystems. It follows the same contract as every other Makefile target: runs inside the dev-toolchain container, reads `.devrail.yml` for language detection, and produces identical results everywhere.
22+
23+
The intended workflow: run `make fix` to auto-remediate, then run `make check` to verify. Anything `make check` still flags after `make fix` requires manual attention -- issues that tools cannot safely resolve on their own.
24+
25+
`make fix` is available in all [DevRail templates](https://github.com/devrail-dev) and existing projects after pulling the latest Makefile.
26+
27+
## Mirror Automation
28+
29+
DevRail maintains repositories on both GitHub and GitLab. Until now, mirroring between the two required a manual `git push <remote> main` after every merge. That step is now automated.
30+
31+
Each repository has a CI job that pushes to its mirror after a successful merge to `main`:
32+
33+
- **GitLab CI** pushes to GitHub using a deploy key stored as a CI variable
34+
- **GitHub Actions** pushes to GitLab using a deploy key stored as a repository secret
35+
36+
The mirror jobs skip gracefully if the secret is not configured, so the CI files work in any fork or clone without modification. If you are hosting DevRail templates on your own infrastructure, see the CI files for the pattern -- it is straightforward to adapt.

0 commit comments

Comments
 (0)