Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/plutotcool/configurations
⚙️ - Base configurations for plutot.cool projects.
https://github.com/plutotcool/configurations
configuration
Last synced: 23 days ago
JSON representation
⚙️ - Base configurations for plutot.cool projects.
- Host: GitHub
- URL: https://github.com/plutotcool/configurations
- Owner: plutotcool
- License: mit
- Created: 2020-11-10T20:33:29.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2023-12-14T13:43:08.000Z (about 1 year ago)
- Last Synced: 2024-11-22T21:55:18.359Z (3 months ago)
- Topics: configuration
- Homepage:
- Size: 126 KB
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: readme.md
- Changelog: CHANGELOG.md
- License: license
Awesome Lists containing this project
README
# Configurations
> Base configurations for plutot.cool projects.
[![current github tag](https://img.shields.io/github/tag/plutotcool/configurations.svg)](https://github.com/plutotcool/configurations/tags)
[![license](https://img.shields.io/github/license/plutotcool/configurations.svg)](https://github.com/plutotcool/configurations/blob/master/license)
## Packages
| name | description |
| -------------------------------------------------------------------------------------------------------------------- | ------------------------- |
| [@plutotcool/typescript-config](https://github.com/plutotcool/configurations/blob/master/packages/typescript-config) | Typescript configuration. |
| [@plutotcool/prettier-config](https://github.com/plutotcool/configurations/blob/master/packages/prettier-config) | Prettier configurations. |## Release
We are using [changesets](https://github.com/changesets/changesets) to create "release intents" for our packages. When those pop up on main a release PR gets prepared automatically and once it gets merged actual release happen (also automatically).
1. [Create a separate branch](https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/managing-branches) for your changes.
2. Create a changeset by running `pnpm changeset`. [More about changesets](https://github.com/atlassian/changesets).
3. Push your branch and open a PR