Skip to content

[HOT FIX | TICKET-PR] DEV.setup: Windows OS - User's prepare script, and internal husky and lint-staged commands fail#20

Merged
Ifycode merged 3 commits intodevelopfrom
@GH-53
Apr 11, 2026
Merged

[HOT FIX | TICKET-PR] DEV.setup: Windows OS - User's prepare script, and internal husky and lint-staged commands fail#20
Ifycode merged 3 commits intodevelopfrom
@GH-53

Conversation

@Ifycode
Copy link
Copy Markdown
Contributor

@Ifycode Ifycode commented Apr 11, 2026

This pull request makes the following changes

General checklist

  • My pull request adheres to the community pull request guidelines.
  • I have read and understood the Pull request guideline extension section found at the bottom of this pull request description/body.
  • I have replaced the dummy text under the subheading Testing checklist below with the testing checklist from the issue ticket I'm working on.

Testing checklist

  • npm run prepare runs the husky init command and set up the git pre-commit hook successfully.
  • The internal husky and lint-staged commands are correctly located, so that the git pre-commit hooks functionality works correctly without issues.
  • The above fixes have been added for Windows OS, without breaking the already working functionalities in MacOS and linux.
  • I certify that I ran my checklist.

How to run project

Find detailed installation guide in the docs.contributors/README.md file of this branch & pull request.

Pull request guideline extension

Note

Do not remove this note or section. This talks about extra things to take note of, in addition to the directions given in the community pull request guidelines.

We appreciate the time taken to help tackle issue tickets our community. Please go ahead to submit your pull request even if it is not yet completed, and push to the pull request actively. This will allow us to know that you have not abandoned the issue ticket. However, you should only alert reviewers about your pull request as explained below, to avoid flooding their GitHub notifications unnecessarily.

"Ready for review" implies that things are working as expected, according to how it is specified in the issue ticket you are working on. Ensure that you test the code that you are working on, that it works as expected. Don't just request for review when your pull request is not yet done and working.

The only time you should be making people review something incomplete is: if you want to show them what's not working, so that they can send help or guidance. If this is the case, be explicit about this in our Discord community or in the comment of your pull request (after you have submitted the pull request).

@Ifycode Ifycode merged commit 777988f into develop Apr 11, 2026
6 checks passed
@Ifycode Ifycode deleted the @GH-53 branch April 11, 2026 18:22
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.

DEV.setup: Windows OS - User's prepare script, and internal husky and lint-staged commands fail

1 participant