SSWConsulting / SSWConsulting/SSW.Rules
🧑💻 Add .EditorConfig check
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 17
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 2
Description
Cc: @tombui99 @adamcogan @william-liebenberg
To Myself,
Currently there is nothing checking that code in PRs follows the standards defined in the .editorconfig file.
- Implement https://github.com/marketplace/actions/editorconfig-action to check this
- Write a rule on this topic
Thanks!
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 repository's .editorconfig file and review the linked editorconfig-action. Resolve whether to implement that action, write a rule, or both, then verify that pull requests report violations of the defined standards. Done means the selected approach checks the stated .editorconfig standards consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100