Consider adding to github/linguist
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.7k
- Forks
- 249
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 23
Description
I noticed that .rhai files don't have any highlighting on github, and that no issues exist about this yet. Github's highlighting is powered by github/linguist, and they allow people to submit new languages if they're popular enough (used in >200 repos). Unfortunately github's search is pretty broken atm so I'm not sure how many repositories rhai is in.
Until github supports it, throwing this in a repo's .gitattributes will highlight it by pretending it's rust:
*.rhai linguist-language=Rust
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked github/linguist CONTRIBUTING guide, especially its instructions for adding a language. Check whether Rhai meets the stated usage threshold of more than 200 repositories, then determine whether the request belongs in github/linguist rather than this repository. Done means .rhai files receive GitHub syntax highlighting without the Rust workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100