You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before you start the task, note that the project uses ESLint and Prettier linters, and also has an .editorconfig.
In your IDE, please provide the paths to their configuration files:
tsconfig.json
.prettierrc.json
.editorconfig
Fork the repository.
Create a new branch from the develop branch. The branch is named after the issue number (for example: 194 or 193-fix-change-detection-bug).
Test the result before you complete the task. We usually write commits in English, the format is something like this:
193. Fix change detection bug in GO search
We kindly ask you to avoid naming commits like fix bug.
When the task is ready, push the changes to your branch. Create a PR from your branch to the develop branch. 3. If possible, discuss the issue on the pull request page.
The person responsible for the project makes a merge in develop, if everything is fine. If you have questions, during the code review you may be asked to fix or improve something.
The text was updated successfully, but these errors were encountered:
const8ine
changed the title
Get familiar with the project
Get familiar with the workflow
Dec 24, 2022
const8ine
changed the title
Get familiar with the workflow
For new contributors: Welcome! Please get familiar with the workflow
Mar 30, 2023
const8ine
changed the title
For new contributors: Welcome! Please get familiar with the workflow
For new contributors: Welcome! Starting with the workflow
Mar 30, 2023
const8ine
changed the title
For new contributors: Welcome! Starting with the workflow
For the new contributors: Welcome! Starting with the workflow
Dec 7, 2023
const8ine
changed the title
For the new contributors: Welcome! Starting with the workflow
For the new contributors: Welcome! Starting with a new workflow
Dec 7, 2023
const8ine
changed the title
For the new contributors: Welcome! Starting with a new workflow
For our contributors: Welcome! Starting with a new workflow
Dec 7, 2023
Working on task
In your IDE, please provide the paths to their configuration files:
Create a new branch from the develop branch. The branch is named after the issue number (for example:
194
or193-fix-change-detection-bug
).Test the result before you complete the task. We usually write commits in English, the format is something like this:
We kindly ask you to avoid naming commits like
fix bug
.When the task is ready, push the changes to your branch. Create a PR from your branch to the develop branch. 3. If possible, discuss the issue on the pull request page.
The person responsible for the project makes a merge in develop, if everything is fine. If you have questions, during the code review you may be asked to fix or improve something.
The text was updated successfully, but these errors were encountered: