-
Notifications
You must be signed in to change notification settings - Fork 42
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
create a workflow using Git Actions #98
Comments
Sure @mansi104-ai. Could you address the current linting errors in the codebase through this ticket as well? |
Sure ,@dvjsharma |
By running manually , you can see the workflows under Github actions |
I don’t think REST APIs would be feasible for lint checks. Instead I’ll suggest a workflow yml file to have trigger dispatch (for manual trigger) and run on any new pushes. Also, if you are using any external tool (which requires installation) you can configure that in codebase. |
Okay, I'll make a yml file in workflows folder in .github . Please assign this issue to me |
Go ahead @mansi104-ai |
@dvjsharma i have experice with MERN stack + TS + nextjs , is there any issue i should work on |
Hey @gopalepic, sorry for late response. There are a lot of high priority issues available currently, please take a look. |
@dvjsharma thankyou so much , it gives me a ray for contribution in your project I requested issue #135 |
Feature Description
We can create a workflow using Git Actions, this workflow will check Lint errors and Type errors in the changes of Pull request. Checking of Lint and Type errors are already implemented in repo and can be run by below command.
pnpm lint && pnpm type-check
Use Case
This feature would check lint errors in the changes of pull request
Benefits
Will benefit the contributors of open source as well the maintainer of the repo in checking the issues of the pull request
Priority
High
Record
-->I agree to follow this project's Code of Conduct
-->I'm a GSSOC'24 contributor
-->I'm willing to provide further clarification or assistance if needed.
The text was updated successfully, but these errors were encountered: