Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Move remaining dev tool config files into @kumahq/config #3211

Open
2 of 5 tasks
johncowen opened this issue Nov 20, 2024 · 1 comment
Open
2 of 5 tasks

Move remaining dev tool config files into @kumahq/config #3211

johncowen opened this issue Nov 20, 2024 · 1 comment
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it

Comments

@johncowen
Copy link
Contributor

johncowen commented Nov 20, 2024 •
edited
Loading

Description

Follow up to #3176

We moved the most useful config files into @kumahq/config which gave us some immediate improvements. But we've decided to move on with some feature work and continue on with moving config into @kumahq/config at a later date.

We should also move:

  • Vite ./packages/*/viteconfig.*.ts
  • Vitepress ./.vitepress/config.*.ts (and related)
  • Makefiles ./mk/
  • lint-staged lintstagedrc.json
  • (maybe more)

And eventually @kumahq/config should become the default for dev tooling configuration files for our application.
@johncowen johncowen added triage/pending This issue will be looked at on the next triage meeting kind/feature New feature labels Nov 20, 2024
@lukidzi lukidzi added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Nov 25, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Feb 24, 2025
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@bartsmykla bartsmykla removed the triage/stale Inactive for some time. It will be triaged again label Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature New feature triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@johncowen @bartsmykla @lukidzi