follow these conventions when contributing to this repository
Branches should be named directly from the corresponding Jira task.
(ex. NCTO-7-ide-vs-code-issue)
[PART] [TYPE] commit message
[COLLAB] [UPDATE] update imports using @ and improve editor manager cleanup
describes what part you're working on in one word
- [ADD] - adding new features
- [REMOVE] - removing features
- [UPDATE] - updating existing features
- [REFACTO] - refactoring wtihout changing functionality
- [CLEAN] - cleaning dead code, comments, imports, etc.
- [FIX] - fixing bugs
We use husky to run linter before each commit, so make sure your code is linted if not it will not be committed.
Init husky by doing bun install ans also bun prepare then you can commit.
To check if your code is linted run bun run lint or bun run lint --fix to fix it automatically simple errors.
describe what was done.
Use GitHub Copilot as reviewer to generate a summary and suggest edits.
Request at least one reviewer.
After each requested change (review feedback), make a new commit and copy the commit ID into the PR comment.