https://github.com/wmde/eslint-config-wikimedia-typescript

ESLint config for TypeScript following Wikimedia code conventions.
https://github.com/wmde/eslint-config-wikimedia-typescript

Last synced: 13 days ago
JSON representation

ESLint config for TypeScript following Wikimedia code conventions.

• Host: GitHub
• URL: https://github.com/wmde/eslint-config-wikimedia-typescript
• Owner: wmde
• License: gpl-2.0
• Created: 2019-11-01T15:13:48.000Z (over 5 years ago)
• Default Branch: master
• Last Pushed: 2025-04-04T11:29:19.000Z (23 days ago)
• Last Synced: 2025-04-04T12:28:05.105Z (23 days ago)
• Language: JavaScript
• Homepage: https://www.npmjs.com/package/@wmde/eslint-config-wikimedia-typescript
• Size: 393 KB
• Stars: 3
• Watchers: 20
• Forks: 0
• Open Issues: 5
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# eslint-config-wikimedia-typescript

ESLint config for TypeScript following [Wikimedia code conventions](https://www.npmjs.com/package/eslint-config-wikimedia) - the idea is to make this repository here obsolete in the medium term and upstream these rules.

## Release instructions

To make a new release:

1. Bump the version number in a pull request.

   (Edit `package.json` manually, then run `npm install` to update the version number in `package-lock.json`.)

   The usual commit message is “Bump version to 1.2.3”.

   [Example pull request](https://github.com/wmde/eslint-config-wikimedia-typescript/pull/48).

1. Get that pull request reviewed and merged.

1. Tag the merge commit locally. A “lightweight” tag is usually enough:

   `git pull`, then git tag v1.2.3.

1. Push the tag. git push origin v1.2.3

1. Turn it into a proper release on GitHub:

   [draft a new release](https://github.com/wmde/eslint-config-wikimedia-typescript/releases/new).

   [Example release](https://github.com/wmde/eslint-config-wikimedia-typescript/releases/tag/v0.2.9).

1. Once the GitHub release is published,

   it should be automatically published to NPM via GitHub Actions.

1. Submit a Gitlab change to `ci-tools/libup-config`

   to update the version of the package in `releases.json`

   ([example](https://gitlab.wikimedia.org/repos/ci-tools/libup-config/-/merge_requests/71)).