This is the public issue tracker for Vale CMS, a CMS for your Vale configurations and assets.
There is no source code in this repository, and there won't be. Vale CMS is a closed-source, commercial product; its code lives in a private repository. This repo exists so that bug reports, feature requests, and the discussion around them are public, searchable, and linkable — the same way they would be for an open-source project.
| What you have | Where it goes |
|---|---|
A bug in Vale CMS (cms.vale.sh) |
Open an issue here |
| A feature request for Vale CMS | Open an issue here |
| A bug in Vale itself — the CLI, a check that misfires, a parser problem | vale-cli/vale |
A question about writing rules, styles, or .vale.ini |
Vale discussions |
| A security vulnerability | Email hello@vale.sh — see SECURITY.md. Do not open an issue. |
| Billing, account, or subscription trouble | Email hello@vale.sh. Do not open an issue; it's public. |
If you can reproduce the same problem in the vale CLI without Vale CMS in the
picture, it belongs in vale-cli/vale.
If it only happens in the app, it belongs here. When you're not sure, file it
here and we'll move it.
Issues here are triaged by the maintainers and fixed in the private repository. That means you'll see the issue get labelled, discussed, and closed, but you won't see the commit that fixed it — the release note or a comment on the issue is the link back. We'd rather have the conversation in the open with that gap than not have it in the open at all.
A well-scoped bug report is a contribution, and it's the kind this repo is built to accept. See CONTRIBUTING.md.
- Vale — the free, local, open-source linter that everything else is built on. Community-owned and unchanged.
- Vale Studio — the free, anonymous, shareable-session playground. Still live, not retired. Report its bugs here too; it has no public tracker of its own.
- Vale CMS — this product. The first Vale Labs project.
Pull requests to this repository will be closed. There's nothing here to change except these documents and the issue templates — corrections to those are welcome, and a PR is a fine way to send one.