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.

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

feat(ref: #112): bun+nodejs, lint-staged #113

Merged
merged 1 commit into from
Jun 19, 2024
Merged

feat(ref: #112): bun+nodejs, lint-staged #113

merged 1 commit into from
Jun 19, 2024

Conversation

lachesse
Copy link
Contributor

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

@lachesse lachesse self-assigned this Jun 19, 2024
@lachesse lachesse merged commit 34c4936 into develop Jun 19, 2024
3 checks passed
@lachesse lachesse deleted the feat/112 branch June 19, 2024 11:33
andriikamaldinov1 added a commit that referenced this pull request Oct 25, 2024
* fix(no-ref): libraries

* fix(no-ref): workflow

* fix(no-ref): workflow

* feat(ref: #112): bun+nodejs, lint-staged (#113)

feat(ref: #112): bun+nodejs, lint-staged (#113)

* fix(no-ref): pre-commit fix (remove bun lint)

* fix(ref:#114): new deps

* feat(ref: #118): enhancement

* feat(ref: #118): update changelog

* feat(ref: #118): remove comments

* feat(ref: #118): add gap

* feat(ref: #118): add gap

* feat(ref: #132): update github actions

---------

Co-authored-by: andrey.levchaev <[email protected]>
Co-authored-by: Andrey <[email protected]>
Co-authored-by: NepipenkoIgor <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants